@markyharris thanks for the quick reply.  Im not too tech savy and am not too sure about editing command lines......so I probably would do option three but am getting this error on your download link:  it says the zip file is in your trash and can't access

Mine says:

# testupdate() # temp fix for server error. More to come

So it seems my software may be current, but I have a different issue that I can't get to the Editor screen?

Can you send me a pic of the error, or possibly the log file? Obviously be sure you are trying the correct IP address. This is shown on the boot up screen if you happen to have a monitor hooked up, or you can use the BerryLan app on your phone to set the WiFi up too.

Let me know what you find, and we'll get it fixed. - Mark

Mark, thank you for having this forum.  I new at this and learning as I go.  I've gotten the IP address from BerryLan, but I get "ERR_Connection_Refused".  Any other thoughts?  I'm using image version 4.373.

Hi, this typically happens because the URL was not properly entered into the web browser. For instance if your RPi's IP address is; 

192.168.1.1 

Then you would have to enter;

192.168.1.1:5000

into your browser to reach the web interface. If you only enter the IP address you will get the error message mentioned. Also, insure that both the RPi and the computer/phone you use are both on the same network otherwise a similar problem will occur.

If you feel you are doing everything properly, attach a picture of the browser and we can try to figure it out together. Let us know. - Mark

@markyharris I tried a few different browsers including my phone.  We have a router set up and I've made sure that I'm logged into the correct network on the computer and BerryLan.  I did get a different message when I logged in directly to the modem.  I got a different error message this time.  The error message said connection timed out (first time it showed connection refused).  I recalled seeing this on earlier posts of the forum.  I went back and tried the three steps you mentioned earlier, but no success.  I've attached screen shots from browsers on my phone and computer.

my phone and computer. 

I am wondering if the URL is wrong. The zero in 192.168.0.114 is normal reserved for router level URL's. I could be wrong but I have never seen this level used for the RPi's.

Please connect a monitor and keyboard directly to the RPi and reboot it. Watch for green text to display and if necessary scroll back up and find the IP address its reporting. It will tell you the exact URL to use in the browser.

Another way to check is to enter your router's admin page and look for 'LiveSectional' in the device list and see what IP address was assigned to it, then use it in the web browser (with the :5000 appended).

If you find that the IP address being reported is in fact 192.168.0.114 then we'll have to dig deeper. Let us know. - Mark

Here's a few screen shots.  I checked the router and the IP address is showing the same for LiveSectional.  Its the same IP address on the BerryLan app. Also, on boot up, I didn't see an IP address.  I've attached a screen shot of what I see on boot up.  There is no opportunity to scroll up.

Ok, then next take a look at the logfile. 

cd /NeoSectional

sudo nano logfile.log

You can copy and paste the bottom portion here for me to look at. Maybe that will show me something. - Mark

Mark,  I've pasted 2 screen shots.  one is the very bottom of the log, but I scrolled up and found an RPI IP address (highlighted in the screenshot)with the appended :5000.  I tried putting that in browser on my phone and computer and still get the "connection timed out".

Good, that's the correct RPi IP so putting it into the browser with the :5000 appended is what you need to do. The fact that you tried this and its still not working tells me you are not on the same network as the RPi. This is further reinforced with the router screenshot you provided showing a different IP address.

You can manually change the network that the RPi is using by entering;

sudo raspi-config

Change the WiFi SSID and Password here then reboot when you are prompted. Just ensure to enter the same network that your phone and/or computer is on. - Mark

Mark, thank you for your continued patience, but it is still not working.  I went into the config file and was careful with the SSID.  It rebooted.  My router and BerryLan are still showing the 192.168.0.114, but when I run the log, it is still showing the RPI address at something different.  Even after the reboot.  I took it one step further.  I flashed as separate SD card to start "clean" and still run into the same thing.  Any other suggestions? One other point.  Earlier, i was getting a "connection timed out".  This latest error message was "connection refused".  Does that mean anything?  

Connection Refused is usually caused because the ':5000" is missing. So just to amplify, it needs to be http://192.168.0.114:5000 for it to work, assuming that's the IP address for the RPi.

Try pinging google to verify that the RPi can reach your network;

ping google.com

Hopefully you will see something like;

pi@livesectional:~ $ ping google.com
PING google.com (142.250.72.174) 56(84) bytes of data.
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=1 ttl=117 time=47.9 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=2 ttl=117 time=45.6 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=3 ttl=117 time=57.6 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=4 ttl=117 time=50.4 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=5 ttl=117 time=45.10 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=6 ttl=117 time=145 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=7 ttl=117 time=46.9 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=8 ttl=117 time=47.3 ms
64 bytes from lax17s50-in-f14.1e100.net (142.250.72.174): icmp_seq=9 ttl=117 time=68.6 ms

This shows successful access to google, and to the internet. Let me know. - Mark

Mark, I did include the :5000 and still no success (see attached). 

I ran the ping google.com command and I think it was stuck in a loop. Is it supposed to stop at some point?  I let it go for about 3 minutes. I got the same messages that you showed in your most recent reply, however, it wouldn't stop. 

I tried pinging 192.168.0.114 from my desktop and attached the message received.  Also, I tried pinging with the :5000 and nothing happened.

Again, I appreciate all your efforts in helping me. 

Ben

Send a pic of the browser with http://192.168.86.33:5000, I'd like to see it if you don't mind. 

The ping command will go on forever. You have to ctrl-c to stop it. Sorry I should have mentioned it.

Another way to set up the map without the interface is to edit the config.py and airports files to match your requirements. It's not a easy but doable. - Mark