You are not logged in.
Pages: 1
Great, as easy as Messing it up in the First Place - Thanks shanin
Also had this issue - for me, it was enough to "Force" the Resolution in the config by Setting it to 1920x1080 instead of Auto-detect (or whatever it's called)
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?
Pages: 1