Build 3011 - Service Unavailable

[Adrian Hudson]

Steve,

I have installed 3011. I now get "HTTP Error 503. The service is unavailable." when trying to connect to the UI.

I have restarted the application and cleared the browser cache and tried different browsers. It doesn't matter if I attempt to connect from a remote PC or the local PC where Cumulus runs.

Any ideas?

p.s. it appears to be operating normally otherwise

[BCJKiwi]

Same here , went back to b3010

[water01]

Well I am exactly the opposite absolutely no problems and it has been running fine for the last 2 hrs on the local connections and the website.

[BCJKiwi]

I am seeing a message in the engine panel which says;
cumulus is running at: //http:/*:8998/
replace * with any ip address on this machine, or localhost.

The Win7 Pro computer has a single network interface which is on a fixed IP address (not obtained via dhcp).
The URL in the service unavailable browser URL does show the correct IP address

It is only the Console (local or over Lan which is affected.

[Adrian Hudson]

I am seeing a message in the engine panel which says;
cumulus is running at: //http:/*:8998/
replace * with any ip address on this machine, or localhost.

Steve appears just to have changed the wording from previous version

[Adrian Hudson]

BCJKiwi, have you added the "netsh http add urlacl" ? I wonder if Steve has done something that has broken it for people who have done that but not for people who haven't...

[Adrian Hudson]

Using http://localhost:8998 on the cumulus machine, works but not http://{ipaddress}:8998 (from anywhere, local or remote)

I can live with that until 3012

[Nykita]

For what it's worth I just got home and downloaded 3011, got it installed and it is running fine on the computer it is installed on, and the other two computers on my local network...

[water01]

Very strange, here is my link to my frontend interface http://192.168.1.75:8998/now.html. IP address works fine.

[BCJKiwi]

BCJKiwi, have you added the "netsh http add urlacl" ? I wonder if Steve has done something that has broken it for people who have done that but not for people who haven't...

Yes you have the answer!!

I did have the url added and used this command to remove it,

Code: Select all

netsh http delete urlacl url=http://<PC IP address>:8998/

and the console now works.

[Adrian Hudson]

BCJKiwi, have you added the "netsh http add urlacl" ? I wonder if Steve has done something that has broken it for people who have done that but not for people who haven't...

Yes you have the answer!!
I did have the url added and used this command to remove it,

Code: Select all

netsh http delete urlacl url=http://<PC IP address>:8998/

and the console now works.

Interesting. That worked for me too. So, it works now, NOT running as administrator and WITHOUT the url reservation.

[steve]

I had no idea that would be a side-effect of listening on all interfaces. It doesn't make sense to me that doing that would no longer require administrator privilege. Do you perhaps still have one of the previous urlacl suggestions set, using '*' or '+'?

[Adrian Hudson]

I had no idea that would be a side-effect of listening on all interfaces. It doesn't make sense to me that doing that would no longer require administrator privilege. Do you perhaps still have one of the previous urlacl suggestions set, using '*' or '+'?

No, I have just checked. No reservations at all for port 8998.

[steve]

I have no reservations for http on port 8998.

If I try to run MX without elevation, I get the 'access denied' error message. If I run it elevated, it works fine. I can connect using a browser using both localhost and IP address.

If I then do netsh http add urlacl url=http://*:8998/ user=\users I can then run MX without elevation. I can connect using a browser using both localhost and IP address.

This is on Windows 8.1.

[Adrian Hudson]

ahh, I know what it is. Remember I run as a service under the local system account.

Still, it does seem that if you put in a reservation for http://an-ip-address:8998/ it causes problems. That is how I had it and removing it fixed it. I will try running as a non admin with the http://*:8998 when I get a moment.