Now it sounds like a firewall setting... Since you get in using SSH (port 22) but are getting no response on HTTP (port 80) or HTTPS (443). Does ping or tracert/traceroute get through to the device. Do you get any connection response if you try telnet to the web server portW5PB wrote: ↑Sat Oct 05, 2019 11:04 pm Thanks for responding, I appreciate the suggestions!
My use of Putty to go in via SSH was done entirely via wifi.
A check of my wifi connections reveals that pi-star is connected, even when I am unable to connect to the dashboard. I have not seen any settings to allow internet only connections. Router is an Ubee DDW36C that came with my Comcast internet package.
{FYI: I do not get a connect on port 443, but do on 80
Code: Select all
C:\Users\Wulfraed>telnet pi-star-3b 443
Connecting To pi-star-3b...Could not open connection to the host, on port 443: Connect failed
C:\Users\Wulfraed>
Just scanning through an edition of the manual for the device:
Advanced/Port Filtering -- are any ports listed? (Though as I understand it, this would block that port for ALL devices and all destinations, both LAN and WAN).
Port forwarding/UPnP settings
Firewall Protection level
DHCP lease time -- manual says default is 3600 (seconds) and recommends 86400. 86400 is 24 hours. If the router doesn't look for devices on a restart, you need the devices to look for it. The 3600 setting would mean DHCP leases expire every hour, and devices would have to request a new lease from the router.