-
Notifications
You must be signed in to change notification settings - Fork 233
Apply Configs Will Not Save. #64
Comments
#65 same issue? |
Nope, I did try your suggestion there. My apply button works, the UI just never resets. Although so far about 1 in 3 installs will actually activate the rest of the modules when I download and install them. There is next to no logging in this. Asterisk is going like crazy but the UI does not seem to log anything. Ether internally or to the browser. Is there a specific host config that is known to work? Like I said, I am using Ubuntu. I dont see a reference to what tiredofit is using. |
Alot of times we have been seeing these upstream errors from Freepbx - I believe I am going to need to switch to a different method and start pinning stable releases to this image as oposed to just pulling from their git repositories. @JAP42 I am using Arch Linux with kernel 5.0, btrfs file systems. |
Yay, Arch, the one linux flavor I have absolutly no experience with. lol. I just tried V14 and although I can apply configs, modules will not properly activate just like 15. I would deffinaly see about a stable branch pulling from a known stable freepbx build. I ended up using fusionpbx because I could not get freepbx working in any senario. Except their own OS which I would prefer to consolidate my services to 1 server which rules that out. Good Luck on the move! |
Hi sorry about the delay, as per the other issue #65 I cannot recreate with a fresh install. This is frustrating. |
I had the same issue. I am new here so I am not sure how to help, but I went on the freepbx source code and replace the code from this file: to the file in container. |
I am trying to set this up on a Ubuntu Based VPS. On a new install I immediately get a "Apply Config" button. It pops the "Restarting" Dialog up and then goes nowhere. I left that going for about 20 mins at one point. I can referesh the page and the settings seem to have applied. But nothing actually works.
All three had the same result. Can not apply settings.
The text was updated successfully, but these errors were encountered: