Suddenly Can't Access Web Server

[Savage1701]

I have Sage 7 Server.

Jetty 2.0.1.19
Web Interface 2.28

On my LAN, I have http://192.168.1.35:8080/sage/home as address that has worked for a month or so now. All of a sudden, nothing, on any computer on my LAN.

I am using sage:frey as default user/password. I have tried uninstalling both and re-installing with restarts of Sage. No help there.

What could have happened? I get to the login screen, type in "sage" and then "frey" but it says incorrect User/Password. Happens with multiple browser types as well - IE 8, FF, Safari. Also, browser caches flushed/cleaned manually.

Realm file shows these as correct.

Thanks for any help.


What could do this? Obviously, I am reaching the Server on my intranet.

[pjpjpjpj]

I'm having similar problems, I posted in the "Mobile Web UI" thread below. Except I'm not even getting to where I can put in a username and password, I am getting "cannot connect to server". As with you, I have not changed a thing, it just stopped working.

It was suggested that perhaps a reboot might have caused the IP address to change - not trying to threadjack, but how do I check that?

[GKusnick]

Run ipconfig at a command prompt on your server to find out its current IP address.

Unless you've taken steps to assign a static IP to your server, then it is subject to change and you should not be using the raw IP as part of the web server URL. Use the server's NetBIOS computer name instead.

If you want to assign a static IP to the server, the best way to do that is through your router's DHCP setup, where you should have the option to reserve a specific fixed IP for a given MAC address.

[Savage1701]

Originally Posted by GKusnick

Run ipconfig at a command prompt on your server to find out its current IP address.

Unless you've taken steps to assign a static IP to your server, then it is subject to change and you should not be using the raw IP as part of the web server URL. Use the server's NetBIOS computer name instead.

If you want to assign a static IP to the server, the best way to do that is through your router's DHCP setup, where you should have the option to reserve a specific fixed IP for a given MAC address.

GK:

That is a static address via my router's table. I use static IP's for all my computers on that network. Much easier. I know the static IP is valid since my extender and clients are set to only look at that IP for the Sage Server and they are fine.

Thank you for the idea; I appreciate it.

[stuckless]

Can you access the webserver from the same machine as the sagetv server by using

http://localhost:8080/sage/

Did you check the sagetv_0.txt log file? Typically there is an entry in there stating that Jetty is starting on a particular port. (search for Jetty or 8080)

Can you ping the address, 192.168.1.35 from another machine on the network?

[Sagebrush]

I get an "error 503: service_unavailable" message.

[Savage1701]

Originally Posted by stuckless

Can you access the webserver from the same machine as the sagetv server by using

http://localhost:8080/sage/

Did you check the sagetv_0.txt log file? Typically there is an entry in there stating that Jetty is starting on a particular port. (search for Jetty or 8080)

Can you ping the address, 192.168.1.35 from another machine on the network?

Same problem - I enter default user and password and it keeps telling me password is wrong.

[stuckless]

Originally Posted by Savage1701

Same problem - I enter default user and password and it keeps telling me password is wrong.

Did you change the password at some point? did you check the username/password settings in the Jetty plugin configuration (I think it's in there). Did you try sage/frey as the default user/pass?

[Fonceur]

From the timing, it could be that the web server was running while the Java update 6.23 was installed, and that messed up some things...

[Savage1701]

Originally Posted by stuckless

Did you change the password at some point? did you check the username/password settings in the Jetty plugin configuration (I think it's in there). Did you try sage/frey as the default user/pass?

It's still sage/frey

[Savage1701]

Originally Posted by Fonceur

From the timing, it could be that the web server was running while the Java update 6.23 was installed, and that messed up some things...

Oh boy, I'm in trouble then; I would have no clue how to fix that. But thanks for the possible trouble area. At least I know it's something I can't fix, if that is the case.

[gplasky]

Originally Posted by Fonceur

From the timing, it could be that the web server was running while the Java update 6.23 was installed, and that messed up some things...

Originally Posted by Savage1701

Oh boy, I'm in trouble then; I would have no clue how to fix that. But thanks for the possible trouble area. At least I know it's something I can't fix, if that is the case.

Just make sure you stop the Sage service. That stops everything including your webserver and just reinstall the java update or repair it. Once that is done fire Sage back up.

Gerry

[archie658]

Originally Posted by Savage1701

I have Sage 7 Server.

Jetty 2.0.1.19
Web Interface 2.28

On my LAN, I have http://192.168.1.35:8080/sage/home as address that has worked for a month or so now. All of a sudden, nothing, on any computer on my LAN.

It seems to be case sensitive now. Use /sage/Home.

[Savage1701]

Well, at least that got me back to the login.

Now I get:

HTTP ERROR 403

Problem accessing /sage/Home. Reason:

User not in required role
Powered by Jetty://

It's frustrating, because all I want to do is manage this on my own intra-Lan network, and it worked well for so long.

[Savage1701]

Originally Posted by gplasky

Just make sure you stop the Sage service. That stops everything including your webserver and just reinstall the java update or repair it. Once that is done fire Sage back up.

Gerry

Gerry:

I don't run Sage as a service, but I will make sure all processes are stopped, etc., and try your advice.

Thanks

[stuckless]

Originally Posted by archie658

It seems to be case sensitive now. Use /sage/Home.

you can just use /sage (and drop the /Home). (The index page will send you to /Home by default)

Originally Posted by Savage1701

Well, at least that got me back to the login.

Now I get:

HTTP ERROR 403

Problem accessing /sage/Home. Reason:

User not in required role
Powered by Jetty://

It's frustrating, because all I want to do is manage this on my own intra-Lan network, and it worked well for so long.

Are you using a custom user/pass? This is an authentication error.

[Savage1701]

No, as far as I know the default sage/frey.

That's what it shows in that file you are supposed to check, anyway.

Unlesss that has changed.