SmartServer IoT Configuration Page Cannot Be Accessed
The SmartServer Configuration page allows you to specify the SmartServer IP address and other hardware configurations. If you cannot access the SmartServer Configuration page, then follow the steps below.
Verify that you are you using https://<smartServer IP address>. http will not work.
Does the web page show an error similar to NET:ERR_CERT_DATE_INVALID when using signed certificates and when entering the following in the URL: https://<smartserver hostname>.echelon.cloud?
This error can indicate that the certificate timed out. The SmartServer will try to automatically renew the certificate, but may not be able to do so.
To continue using signed certificates, manually re-new the certificate using KB1455.
Alternatively, you can use the SmartServer IP address instead of the SmartServer hostname.
You may see not be able to access the SmartServer Configuration page and CMS if the HTTP and HTTPS ports changed from the defaults.
In this case, you can ping the SmartServer, but not access the SmartServer Configuration page or CMS.
Issue the following console command: sudo grep "listen" /etc/nginx/sites-enabled/apollo.conf. The line with ssl should show 443 and there should be two lines showing 80.
If 443 and 80 are not shown then you may need to change the apollo.conf file to use the default ports. See Managing SmartServer IoT Ports and Services.
Verify whether the SmartServer is constantly rebooting by looking at the SmartServer console port.