Jump to content

Under construction


James
 Share

Recommended Posts

Hello,

 

I'm having a problem where the PBX web site will not work unless you access the site from the server itself. If you try and browse the site from a client on the network you receive a website under construction page. The sites were working previously and I’m confused as to why this would suddenly stop working.

 

We are running server 2003 r2 with pbxnsip 3.4

 

Any help would be great, although I know this more likely to be an IIS problem.

 

Thanks

James

Link to comment
Share on other sites

Hello,

 

I'm having a problem where the PBX web site will not work unless you access the site from the server itself. If you try and browse the site from a client on the network you receive a website under construction page. The sites were working previously and I’m confused as to why this would suddenly stop working.

 

We are running server 2003 r2 with pbxnsip 3.4

 

Any help would be great, although I know this more likely to be an IIS problem.

 

Thanks

James

 

As long as you have the right IP:port, it should work. Maybe as you think, it maybe the IIS showing you this page.

Link to comment
Share on other sites

As long as you have the right IP:port, it should work. Maybe as you think, it maybe the IIS showing you this page.

 

IIS is showing me the page. The problem seems to be that IIS is not forwarding the requests to the pbxnsip service. The site is setup to us port 80 in IIS. It’s also set to use the default website, although I can’t seem to find where this site is actually located. There is no host header configured, but I’m sure this is correct.

 

Is there anyone who understands the mechanics of how or what IIS is forwarding the request to? I’m at complete loss as to what I could try next...

Link to comment
Share on other sites

Is there anyone who understands the mechanics of how or what IIS is forwarding the request to? I'm at complete loss as to what I could try next...

 

:blink: IIS forwarding the request?! It should not... The PBX is running its own web server on a different port. For example, if the PBX runs it's service on port 8080, then you would use a HTTP URL like this: http://192.168.1.1:8080 (the http:// part is important for most browsers).

 

You can try to let the IIS server send a 302 redirection code when accessing a certain page, then the web browser would go to the PBX after the redirection.

Link to comment
Share on other sites

:blink: IIS forwarding the request?! It should not... The PBX is running its own web server on a different port. For example, if the PBX runs it's service on port 8080, then you would use a HTTP URL like this: http://192.168.1.1:8080 (the http:// part is important for most browsers).

 

You can try to let the IIS server send a 302 redirection code when accessing a certain page, then the web browser would go to the PBX after the redirection.

 

 

Thanks for you help. As you can probably tell I'm new to pbxnsip and I've had just figured out where I have been going wrong. The problem lies in that IIS was interfering with the pbxnsip web server. The IIS default web site was hijacking port 80 and stopping the external requests for reaching the pbxnsip web service on port 80. Disabling the default website fixed the problem.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...