The built-in HTTP Server is not listening on port xx
-
- Posts: 8
- Joined: Thu Feb 18, 2016 12:47 pm
The built-in HTTP Server is not listening on port xx
After I reboot my server, I found this problem is appear. how to fix it?
Before reboot my server, everything is working well.
Before reboot my server, everything is working well.
Re: The built-in HTTP Server is not listening on port xx
Hello,
Have you tried restarting your web services manually ? Possibly the port 82 may be already in use, you can verify this information with the netstat -na command, in which case switching to a different port will solve this issue.
Have you tried restarting your web services manually ? Possibly the port 82 may be already in use, you can verify this information with the netstat -na command, in which case switching to a different port will solve this issue.
Olivier
TSplus support team administrator
TSplus support team administrator
-
- Posts: 8
- Joined: Thu Feb 18, 2016 12:47 pm
Re: The built-in HTTP Server is not listening on port xx
Hello Sir,
I tried to restarting web service, server so many times already. It's not working well.
And the port 82 must not be using in whole network too. Please find my "netstat -na" result as below:
------------------------------------------------------------------------
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2638 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3391 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6203 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6247 0.0.0.0:0 LISTENING
TCP 0.0.0.0:19955 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49163 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49164 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2638 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5939 127.0.0.1:49161 ESTABLISHED
TCP 127.0.0.1:49161 127.0.0.1:5939 ESTABLISHED
TCP 192.168.0.96:139 0.0.0.0:0 LISTENING
TCP 192.168.0.96:49185 217.146.1.42:5938 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:2638 [::]:0 LISTENING
TCP [::]:3391 [::]:0 LISTENING
TCP [::]:19955 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49163 [::]:0 LISTENING
TCP [::]:49164 [::]:0 LISTENING
TCP [::1]:2638 [::]:0 LISTENING
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 127.0.0.1:2638 *:*
UDP 127.0.0.1:2638 *:*
UDP 192.168.0.96:137 *:*
UDP 192.168.0.96:138 *:*
UDP 192.168.0.96:2638 *:*
UDP 192.168.0.96:2638 *:*
UDP [::]:500 *:*
UDP [::]:4500 *:*
UDP [::]:5355 *:*
------------------------------------------------------------------------
I tried to restarting web service, server so many times already. It's not working well.
And the port 82 must not be using in whole network too. Please find my "netstat -na" result as below:
------------------------------------------------------------------------
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2638 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3391 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6203 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6247 0.0.0.0:0 LISTENING
TCP 0.0.0.0:19955 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49163 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49164 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2638 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5939 127.0.0.1:49161 ESTABLISHED
TCP 127.0.0.1:49161 127.0.0.1:5939 ESTABLISHED
TCP 192.168.0.96:139 0.0.0.0:0 LISTENING
TCP 192.168.0.96:49185 217.146.1.42:5938 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:2638 [::]:0 LISTENING
TCP [::]:3391 [::]:0 LISTENING
TCP [::]:19955 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49163 [::]:0 LISTENING
TCP [::]:49164 [::]:0 LISTENING
TCP [::1]:2638 [::]:0 LISTENING
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 127.0.0.1:2638 *:*
UDP 127.0.0.1:2638 *:*
UDP 192.168.0.96:137 *:*
UDP 192.168.0.96:138 *:*
UDP 192.168.0.96:2638 *:*
UDP 192.168.0.96:2638 *:*
UDP [::]:500 *:*
UDP [::]:4500 *:*
UDP [::]:5355 *:*
------------------------------------------------------------------------
Re: The built-in HTTP Server is not listening on port xx
Hello,
Have you tried connecting with HTTPS://yourserver.com:445 ?
Uninstall java and delete the java folder located in C:\Program Files x86\ and C:\ProgramData (this is a hidden folder) then reinstall java 64 bits on the server. Once this is done, restart your web service again.
Have you tried connecting with HTTPS://yourserver.com:445 ?
Uninstall java and delete the java folder located in C:\Program Files x86\ and C:\ProgramData (this is a hidden folder) then reinstall java 64 bits on the server. Once this is done, restart your web service again.
Olivier
TSplus support team administrator
TSplus support team administrator
-
- Posts: 8
- Joined: Thu Feb 18, 2016 12:47 pm
Re: The built-in HTTP Server is not listening on port xx
Hello, test with https://127.0.0.1:445, it's fail again.
And then, I was re-install the java 64bits on my server. Then, restart the whole server again. I got the same problem.
And then, I was re-install the java 64bits on my server. Then, restart the whole server again. I got the same problem.
Re: The built-in HTTP Server is not listening on port xx
Hello,
This means another application is conflicting TSplus web server. Have you reinstalled Java as suggested ? Could you try with a different set of port ?
You need also to check that the BrandCache service is disabled as it is not compatible with TSplus web services.
This means another application is conflicting TSplus web server. Have you reinstalled Java as suggested ? Could you try with a different set of port ?
You need also to check that the BrandCache service is disabled as it is not compatible with TSplus web services.
Olivier
TSplus support team administrator
TSplus support team administrator
-
- Posts: 8
- Joined: Thu Feb 18, 2016 12:47 pm
Re: The built-in HTTP Server is not listening on port xx
Hello Sir,
- Yes, I was reinstall the Java already. My Java version is show on attached picture.
- I tried the orginial port 80 already, the problem is same.
- My windows did not install the BrandCache Service.
- Yes, I was reinstall the Java already. My Java version is show on attached picture.
- I tried the orginial port 80 already, the problem is same.
- My windows did not install the BrandCache Service.
-
- Posts: 8
- Joined: Thu Feb 18, 2016 12:47 pm
Re: The built-in HTTP Server is not listening on port xx
Problem Solved. Thanks!
Re: The built-in HTTP Server is not listening on port xx
Solved? How...would be interested to know as I am a Newb with the same problem!
edit: Solved for me with the Java reinstall 64bit. Thx Olivier!
edit: Solved for me with the Java reinstall 64bit. Thx Olivier!
Re: The built-in HTTP Server is not listening on port xx
Please let me know how do you solved, I have the same problem