Search results

OK got it, didn't see the second module.

Interesting, I didn't realize it was a commercial module. I have removed it, but the error persists in the dashboard. Shouldn't it be removed there as well?

I have tried installing both Debian and Rocky on Digital Ocean and Vultr with 1 CPU, 2GB RAM and 50GB SSD. All them give the same error. I have tried running fwconsole restart on all instances with no luck. I always got these replies as well Clearly Client Server is not running and No valid...

Any word on 19? :)

If we go with 16, is there a possibility to upgrade later?

Thanks for that. I have been running a regular build of Rocky, then running the stand alone installer for Incredible PBX so I didn't notice any changes.

yeah the status page is correct now after a reboot. Another issue is that ./add-fqdn or ./add-ip isnt adding anything to the iptables ruleset and iptables in general is really barren compared to past builds.

And I know this has gotten off the original topic, but it doesn't look like webmin was installed

One other thing I noticed on both Vultr and DO is that after the installer completes it actually changes the hostname of the system to noreply.incrediblepbx.com. I can manually change it back, but I don't recalling seeing that behavior in past builds.

No love.....same error on DO. I'll just use pw.

I used the latest build of 18 as of yesterday. I will try again today with that command.

Now this is really interesting.....

Just installed on Vultr and it does something similar with the ssh key, however it at least falls back to password auth as Vultr still creates a root password when you spin up an instance. I will say that I did also create a password for root on DO, but it would never fall back to that. UPDATE...

Well, shoot. I never had it happen on previous pbx installs, but it has been a while.

I thought that at first too, so I made sure to run yum update after the initial build of the droplet and before running the Incredible installer. I have also tried not running yum update after the build and going right to the installer. Same result.

When building the droplet Digital Ocean allows you to specify your key at that time. This is how I have always built droplets with them for many years and never had a problem with any installs until this one.

I can duplicate this on every install and I have installed over 10 times with the same exact result. Using Digital Ocean, I spin up a Rocky 8.5 standard droplet with Intel CPU and use SSH Key for login. It works absolutely fine after the droplet is created, I do yum updates, reboots etc. Every...

Same screenshot as in my original post I just changed from host with a FQDN to host with an IP address.

Figured it out. With Flowroute switching to a range of IPs for each the new POPS the entry of host=us-east-NJ.sip.flowroute.com doesn't seem to work that well for this version of Incredible. I know it's old, but the systems have been up and running flawlessly (knock on wood) for over 4 years...

Hey all, been a while since I have been here and now I need some help. With Flowroute retiring the LV POP I have been working on getting the new POPs setup and I have been successful for outbound without issue, but I cannot get inbound working. I am still on Asterisk 13.21.0, Incredible GUI...