You are not logged in.
Hi, dear shahin
upgraded to build 2314 and now have error 500 and " Could not connect to the NanoDLP. Please check your network connection" message. this problem is when i connect by wifi or LAN with my pc or laptop but when i use my mobile phone everything is ok. in former build i didn't have this problem. also it happens randomly and page loads with lags. also ssh works fine and here are sudo ./printer results:
2019/09/03 12:43:09.158148 {"Layer":"0","module":"Hardware","level":"Notice","ms g":"Initializing build # 2314 - generic"}
2019/09/03 12:43:09.226053 {"Layer":"0","module":"Terminal","level":"Notice","ms g":"Terminal Reader Activated"}
2019/09/03 12:43:09.231455 {"Layer":"0","module":"Server","level":"Error","msg": "Could not setup server. listen tcp :80: bind: address already in use"}
Offline
It indicates another nanodlp already running. Kill it using "sudo killall printer" and rerun see when it throw error.
Offline
did sudo killall printer, upgraded to 2335, problem not solved yet. cleared browser history and data completely not working. at the bottom of main page red box displays "error (500) accessing requested source/info" had no issue with build 1819.
Last edited by F.m (2019-10-07 11:34:15)
Offline
Not sure why, looks like your interface files are newer than the installed binary.
Offline
what do you mean? i just installed build 1819 image file and upgraded it to latest stable build 2335.
Last edited by F.m (2019-10-12 14:12:11)
Offline
Looks like binary file is not upgraded correctly
Offline
right, then what is your recommendation? also i must inform you that, these problem exist on windows ver too. my windows is 10, 64 bit with avira antivirus.
Last edited by F.m (2019-10-13 10:48:08)
Offline
it seems that nano dlp tries to connect to internet to show descriptions about new version. when internet is reachable everything is ok but otherwise, error occurs.and when the mouse hovers over nano dlp tab, displays: "nanodlp error error error ........ " is there any way to cancel this feature. in previous releases this problem didn't exist.
Last edited by F.m (2019-10-19 14:30:59)
Offline
Try latest beta see if it fixed the issue or not.
Offline