You are not logged in.
Pages: 1
If you cannot not access web interface of your device after installation,
SSH into your device
cd /home/pi/printer
sudo ./printer
If the output contains line below, everything on program side is working fine. Probably there is a browser issue.
2016/02/25 10:54:42.066588 {"Layer":"-","module":"Hardware","level":"Info","action":"Initialization","msg":"-"}
2016/02/25 10:54:42.066786 {"Layer":"-","module":"Terminal","level":"Info","action":"Terminal Reader Activated","msg":""}
panic: listen tcp :80: bind: address already in use
If the output indicate no error, now you should have access to web interface. It is probably a networking or startup script issue.
2016/02/25 10:54:42.066588 {"Layer":"-","module":"Hardware","level":"Info","action":"Initialization","msg":"-"}
2016/02/25 10:54:42.066786 {"Layer":"-","module":"Terminal","level":"Info","action":"Terminal Reader Activated","msg":""}
Run "ifconfig -a" and send report back to us.
If the output contains other errors, the most probably the program hast a bug. Please share output with us.
If the printer crashed during your print, or something else is wrong with your printer software
Go to setup page
Tools tab
Press debug info button and attach exported zip file.
Offline
Hi,
Does it make sense the printer.log file is about 3,5 GB?
Offline
Which build do you use?
Actually it reported before and I hope we have fixed this issue. It happens whenever communication issue raise. If you are not on latest version please upgrade.
Offline
Offline
On the latest version we have ability to prevent log flood, for example if your RAMPS board keep sending same messages again and again it stop displaying those messages.
Will fix the UI problem on the next version, thank you.
Offline
Hey similar issue here: wanted to set up the windows nandlp as external slicer, so i changed the listening port in the Raspberry-nanodlp to 8080 (thought it needed to be the same as the windows one with 127.0.0.1:8080
well...now i can't access my web interface anymore and get this message via ssh when trying to start nanodlp:
2017/12/29 12:00:29.696766 {"Layer":"155","module":"Hardware","level":"Notice"," msg":"Initializing build # 1744 - generic"}
2017/12/29 12:00:29.702590 {"Layer":"155","module":"Terminal","level":"Notice"," msg":"Terminal Reader Activated"}
2017/12/29 12:00:29.704399 {"Layer":"155","module":"Server","level":"Error","msg ":"Could not setup server. listen tcp :8080: bind: address already in use"}
any easy way of resetting the setup-changes?
Offline
No need to change rpi port.
SSH into rpi and edit file below and change port
/home/pi/printer/db/machine.json
Offline
Great, as easy as Messing it up in the First Place - Thanks shanin
Offline
I have the same problem
how to put it right
/home/pi/printer/db/machine.json in putty ?
pi@nanodlp:~ $ /home/pi/printer/db/machine.json
-bash: /home/pi/printer/db/machine.json: Permission denied
pi@nanodlp:~ $
what is not correctly written?
How can I put it right?
found
sudo nano /home/pi/printer/db/machine.json
Last edited by elshad66 (2017-12-29 19:12:28)
Offline
Pages: 1