Cannot access Webadmin
#1
Hi all!

I have configured webadmin.ini properly with the username and password, but I keep running into "invalid request" when I try to access localhost:8080.

My Chrome browser gets a 400 error whenever I attempt to access it. MCServer also does not pick up any activity of me accessing webadmin either.
I cleared all my caches and cookies, but I still got the same error.

The server also has a message:
Code:
WebServer: The server is running in unsecured HTTP mode.
Put a valid HTTPS certificate in file 'webadmin/httpscert.crt' and its corresponding private key to 'webadmin/httpskey.pem' (without any password) to enable HTTPS support

I am fairly new at this, so excuse my ignorance. Blush
Reply
Thanks given by:
#2
You're lacking information like:
1) Operation System
2) Pre-compiled or self-compiled
3) revision of MCServer (or the url to the download page)
4) content of the webadmin.ini

just for reference, error 400 means "bad request" and is normally cause from a client (browser) sending a "bad requests" to the server.
http://www.checkupdown.com/status/E400.html
Reply
Thanks given by:
#3
I am using Windows 7 64bit.
Pre-compiled. I downloaded the corresponding file of MCServer from the main page.

webadmin.ini content:
Code:
[WebAdmin]
Port=8080
PortsIPv6=
Enabled=1

[User:Admin]
Password=pass
Reply
Thanks given by:
#4
Are you sure that you're connecting to the right port (8080) and the right IP? (Probably localhost)
Reply
Thanks given by:
#5
(01-06-2015, 05:24 PM)bearbin Wrote: Are you sure that you're connecting to the right port (8080) and the right IP? (Probably localhost)

Yup, I used localhost:8080 on the same machine running MCServer.
I also double checked to see if my ports are forwarded correctly too.
Reply
Thanks given by:
#6
MCServer shouldn't be able to return a 400 code, it will generally return 500 codes. Probably there is some other server already running on the port. However there is the possibility that Chrome has broken something in the HTTP server, in which case we'd need the chrome version you're using and preferably the what the raw requests and responses are which you should be able to get through Chrome dev tools.
Reply
Thanks given by:
#7
Actually, I just tried to access webadmin again, and this time it is working properly!
I didn't do anything at all, nor have found the cause.

I really do appreciate everyone helping me out, thanks everyone!! Smile
Reply
Thanks given by:
#8
One thing that comes to my mind is the http / https mismatch. From what you've quoted from the server log, you haven't prepared the private key and certificate, so MCServer is running in http mode. Were you, by any chance, trying to access https://localhost:8080 instead of http://localhost:8080 ? Worktycho's observation could be another cause. When you stop MCServer and issue a "netstat -na" command inside the command prompt, is port 8080 listed as listening?
Reply
Thanks given by:
#9
I made sure I was accessing http://localhost:8080. My chrome version is 39.0.2171.95 m. I checked the "netstat -na" command and 8080 is listed as "Time Wait".
Reply
Thanks given by:
#10
he is not asking about the port but about http:// vs https://
Reply
Thanks given by:




Users browsing this thread: 3 Guest(s)