View Full Version : HTTP 500 Internal server Error
handycam
05-04-2008, 04:39 AM
Hello to everyone,
I receive the error "HTTP 500 Internal Server Error"
after login, while I try access to web user interface in
a new NanoStation2. I can ping it to 192.168.1.20
and Ubiquiti Discovery tool show me the device in
Dicovered Devices. I already configured another NS2
withouth problem and I think I am doing nothing wrong.
How can I solve this problem?
TIA
Antonello.
handycam
05-05-2008, 03:32 AM
I solved the problem.
I write here the workaround for someone who will need.
Maybe the module index.cgi loaded after login window was
corrupted, so in the "HTTP 500" error page I changed the address
http://192.168.1.20/index.cgi to http://192.168.1.20/system.cgi
then I updated the firmware to AirOS3.
Now the NanoStation2 is working fine.
Antonello.
MultiTricker
09-18-2008, 01:55 AM
Thank you! This was very helpful and saved me.
UBNT-Mike.Ford
09-18-2008, 02:02 PM
Thanks for the update.
Mike
rmssystems
10-20-2008, 12:27 AM
hi,
you can also flash the newest firmware via tftp. helps :)
DrNutbush
10-20-2008, 02:57 AM
I also receive the error often from new Nano's in Firefox. 99% of the time will work in IE though...
UBNT-Mike.Ford
10-20-2008, 02:36 PM
Hey Guys,
You might recieve this error with units with 2.2.1 on them. You can get around it by typing the IP and adding network.cgi to the end so:
192.168.1.20/network.cgi
Then upgrade the units to the latest software and the problem will be gone.
Thanks,
Mike
lahoras
11-01-2008, 08:35 PM
Mysteriously, I clean my browser cache and fix the problem, do not understand which might be the problem, but doing it work fine.
greetINGS
ARIEL
UBNT-Mike.Taylor
11-01-2008, 11:50 PM
The top level URL of AirOS returns a redirect to the main status page.
If witch out a device with 3.x firmware on it for a device with 2.x firmware on it then the cached redirect is returned, pointing you to a URL that is only valid on the 3.x firmware.
This only hits you if you are swapping between 3.x and 2.x devices on the default IP address, for example.
The simplest workaround is to clear your browser cache - but we have filed a bug for this and it be fixed in a future release.
CharlesA920
01-07-2009, 03:52 PM
I got in a batch of NS2 today and was flashing them with the -rc version and ran into this problem.
After a short panic I searched and found this thread. which solved the problem.
:D
UBNT-Mike.Ford
01-07-2009, 05:12 PM
Good to hear!
Mike