Port: 5000 for provisioning not defined in nginx.conf

Status
Not open for further replies.

Enoch

Customer
Joined
Mar 5, 2015
Messages
42
Reaction score
2
Need some help with nginx.conf configuration. When I try to access the default provisioning link:

http://10.0.1.1:5000/provisioning/{randomc_code}/phonebook.xml

I get an IIS HTTP Error 404.0 - Not Found

The file does exist in provisioning folder:

C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\{randomc_code}\phonebook.xml

So this leads me to suspect because the path is not defined in the nginx.conf hence the reason it is not working.

BUT for some reason the a https link works and I've looked into nginx.conf and nothing is defined for the provisioning folder:

https://10.0.1.1/provisioning/{randomc_code}/phonebook.xml

So to define the /provisioning folder within nginx.conf do I just add the following into the listen 5000 section?

location /provisioning {
include "shared-headers.conf";
alias "C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\";
}

Am I missing anything?

Then after it has been defined, how to I restart nginx to the configuration loads?
 
You do realize that you said you get an IIS error right? So if you are getting an IIS error, it doesn't have anything to do with 3CX/Nginx, it has to do with IIS listening on that port.
 
  • Like
Reactions: JohnS_3CX and nub
Also, I noted that you said http was on 5000, but https on 443. Typically it would be 5000/5001 or 80/443 so I would confirm whether you should be using 5000 or 80
 
  • Like
Reactions: Lee Cramman
You do realize that you said you get an IIS error right? So if you are getting an IIS error, it doesn't have anything to do with 3CX/Nginx, it has to do with IIS listening on that port.
Yes, that is part of my confusion. IIS on this server is not setup to listen on port 5000. Hence for it to be responding is weird.

Can I get some confirmation that 3CX is actually using Nginx as the webserver and not IIS
 
Also, I noted that you said http was on 5000, but https on 443. Typically it would be 5000/5001 or 80/443 so I would confirm whether you should be using 5000 or 80
I didn't say http was on port 5000. I just said the provision link points to port 5000 and when accessed it gives a http error.

And for some reason, https:// (without :5000) works. Even though the path was not setup within Nginx config.
 
The current version of 3CX does indeed use NginX so, under normal circumstances, IIS should not even be installed.

I could go ahead and recommend actions such as removing IIS, reverting any changes in the nginx.conf, confirming the configured HTTPS/HTTP ports, etc, but to be completely honest, I think your best option now would be to simply take a backup and reinstall so that you start with a clean sleight and ensure your 3CX instance is running a supported configuration.
 
  • Like
Reactions: NickD_3CX
Status
Not open for further replies.