Unable to access localhost:8998

TideMan · Post by **TideMan** » Fri 01 Apr 2016 3:17 am

I've been mucking about with my RPi3 running Jessie and now I can't access localhost:8998
CumulusMX is working fine logging data every 10 min, but I can't access the console any more.

How can I get it back?

Post by **freddie** » Fri 01 Apr 2016 8:51 am

Have you tried 127.0.0.1:8998?
Can you zip/upload the contents of your MXdiags folder? Or failing that post a copy/paste or a screenshot of your console that shows MX starting up?

jank · Post by **jank** » Fri 01 Apr 2016 5:33 pm

Can you access the GUI from your Windows Box? Or from any Remote Computer?

TideMan · Post by **TideMan** » Sat 02 Apr 2016 2:53 am

jank wrote:Can you access the GUI from your Windows Box? Or from any Remote Computer?

No. I can see http://rpi3.local, but htpp:/rpi3.local:8998 does not show.

TideMan · Post by **TideMan** » Sat 02 Apr 2016 2:58 am

freddie wrote:Have you tried 127.0.0.1:8998?
Can you zip/upload the contents of your MXdiags folder? Or failing that post a copy/paste or a screenshot of your console that shows MX starting up?

Well I never...................
I just opened the mxdiags file and the top line said -port 9999
When I tried that port, it worked!!
How did the port number come to change I wonder?

Post by **steve** » Sat 02 Apr 2016 2:32 pm

That comes from the command line that you are using to start Cumulus.

jank · Post by **jank** » Sun 03 Apr 2016 9:42 am

steve wrote:That comes from the command line that you are using to start Cumulus.

Port 9999 sounds a little bit like - he is using an older version of my start|stop script.
I am using Port 9999 at home and sometimes when updating my start/stop script here in the forum, I forget to change back to the default port 8998.
But the most current version should have 8998 as default port

TideMan · Post by **TideMan** » Mon 04 Apr 2016 3:18 am

jank wrote:
steve wrote:That comes from the command line that you are using to start Cumulus.
Port 9999 sounds a little bit like - he is using an older version of my start|stop script.

Yes, I am using your script jank.
But I thought I'd downloaded the latest one - 2.5.0.0 (2016-02-19)

philpugh · Post by **philpugh** » Tue 05 Apr 2016 5:41 pm

Yes indeed. The 2.5.0.0 .sh file does have port 9999 in it. It threw me for a few mins as well!

jank · Post by **jank** » Wed 06 Apr 2016 6:56 pm

philpugh wrote:Yes indeed. The 2.5.0.0 .sh file does have port 9999 in it. It threw me for a few mins as well!

F*** this is not the first Time where I uploaded the script with Port 9999 in the Settings file.

....meanwhile i checked the conf file and indeed, there is a line like

# TCP Port CumulusMX is running (Default TCP Port - 8998)" >> /CumulusMX/cumulusmxsh.ini
PORT=9999

..normally, when you update the script from version 2.4.x to the next higher version, there is no need to extract also the conf file and overwrite your existing one.
The reason why I switched to a config file was, that people can stay on their settings without modifying the main script file each time I have an update.
When updating to the next higher version, don't touch your settings file and overwrite it with the one in the update zip.
New settings will be automatically added to the conf file when not already present. Existing settings will not be overwritten.

Cumulus Support

Unable to access localhost:8998

Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998

Re: Unable to access localhost:8998