Maj, I should also mention that the guy doesn’t mention which user to be logged in as in the guide, can’t cd anything since it’s a shell command, so I had to figure out the hard way I have to be logged in as root, which still exists, for some reason… even though I read somewhere that root was disabled…
UPDATE: Even after a clean reinstall… it doesn’t work… not sure why, all I get is the same error from last time, and something about an error code 2 “Invalid Argument”…
UPDATE 2: Returned the old in.tftpd as the main one, and it works fine, so something tells me the modified one is broken somehow…
UPDATE 3: The firewall was blocking the Windows TFTP client even when off, made an exception and it works… more as the situation develops…
UPDATE 4: Reinstalling the system for like the 6th time… getting kinda sick of this now, wish it’d just work…
UPDATE 5: Reading through the guide once more, I’ve discovered that the guide prescribed simply WILL NOT work with the most recent version, so I come with a question: Shall I downgrade an FPBX17 version? Mini-Update: I’m noticing the guide was created BEFORE FPBX17, because the oldest release dates to March 2025, do users get to edit posts in topics after it closes/locks? I imagine not…
UPDATE 6: I’m very tired… I stayed up way later than I wanted to… but I did a sanity check just to make sure I wasn’t losing my mind, and I might’ve found the solution to my problem… but before I can share it, I wanna run it on the latest version, and to do that, I want to sleep first… and it relies VERY HEAVILY on it actually WORKING… will update when the time arises… so for anyone tuning in right now, a solution to the issue is around the corner and a sleep away as of writing this… stay tuned!
FINAL UPDATE: Despite running on just 4H of sleep and some pop tarts for breakfast, I’ve gotten it going now… So for those who are just tuning in, welcome. If you’re in a similar situation I’m in, I have the solution now: Getting this to work on FPBX16 is IMPOSSIBLE, just upgrade to 17, I know 16 was better in some ways, but go up a version if you need this working. Let’s start there. Secondly, if you haven’t checked out the other thread “Installing FreePBX 17 on Hyper-V virtualization platform”, go check that out real quick, basically just perform some checks on your host system and with your VM platform while the guest machine is off. Anyway, The solution here is to ensure that you DON’T install the modified TFTPD client as ROOT, you will pull your hair out trying to get it to work, instead, only do the first few steps of the linked guide in this thread as root, once you get to doing apt-get source whatever, STOP BEING ROOT! Just sudo everything that needs to be done as sudo, so basically anything you can do NORMALLY, just do it without sudo, then obviously once that’s all set up, you gotta chmod the /tftpboot directory to 777, then chmod -r 666 everything inside of that, then just configure the softphone like normal (as admin obviously), and away you go.
This was VERY painful and heartbreaking as I loved 16 for the familiarity I had with whatever version I was using back in 2020, but… progress, I suppose. Needless to say, I got it all worked out now, and now I’m prepared for when the future throws this challenge at me again.
Also, word to the wise: MAKE BACKUPS OF THE MODIFIED FILES AS WELL! If you don’t, and TFTPD on FPBX constantly fails to start with no error, your in.tftpd file is MISSING! Had to learn that the hard way last night… Thankfully the fix was mostly easy… just had to remind myself to cp some stuff instead of mving it…
One more thing: I’d be extra cautious when doing this, even with the firewall wizard having been ran, apparently you can STILL set off Fail2Ban… somehow…
And I must say, my review for the assistance rendered to me: My first time back in about five years, not a bad experience, obviously I’d make a few minor tweaks, but in the grand scheme of things, I’d give it 4.75/5 stars