Single and Confused
#1
I need help using Webadmin and setting up ip/port. I looked on the book, wiki, and forums, and there is no explanation. I know something about generating an https, but the program says "Openssl is not a internal or external command, operable program, or batch file. Please help immediately!
Reply
Thanks given by:
#2
Are you running windows? The command invoking openssl was almost certainly written for linux/OS X. If you don't mind the lack of security, the server will host the webadmin with http if it can't find a certificate.
Reply
Thanks given by:
#3
I guess a better way to form the question is How do I set up my ip for the server, and how do i use Webadmin
Reply
Thanks given by:
#4
If you want to run the server on your home network and want it also accessible from the internet, you need to set up port forwarding. This differs, depending on your router's make and model, you need to consult your router's manual for details on how to do it. For minecraft, you need to forward port 25565. If you want to use webadmin from the outside too, you need to additionally choose one port (in webadmin.ini) and forward that port as well.

When using webadmin from the outside, it is highly recommended that you use an https version of the page, which means you need to generate a certificate. There are two scripts, one for Windows, the other for Linux. In order for the windows' script to work, you need to install OpenSsl windows binaries, available from https://slproweb.com/products/Win32OpenSSL.html for example (the Light package is enough).
Reply
Thanks given by:
#5
So it looks like the problem was with the router, but it is fine now. But the thing is, when people try to connect, they get "Am existing connection was forcibly closed by the remote host", any ideas?
Reply
Thanks given by:
#6
I think your network setup is not working properly yet, perhaps the port is forwarded to a different machine or a different port, or a firewall could be stopping the traffic (although usually firewalls make the connections time out, rather than forcibly closed).

Start the server with "--log-comm" parameter, this will make it log all connections, each into a separate file in the "CommLog" folder. Look there if there is any connection attempt from the external address. If there is, great, the connection is getting through and something in the server keeps dropping it, post the logfile here. If there isn't one, it's your network setup that's at fault.

(btw interesting choice of topic title, that's exactly what I would call myself nowadays Smile )
Reply
Thanks given by:




Users browsing this thread: 5 Guest(s)