Can't connect to Recalbox
-
@oluminion are you using PI3 internal wifi ?
-
@oyyodams
No the RPi3 is connected via cable over dLAN with the router. -
Ok after several reinstalls and tests, things changed a bit but not yet good.
I can connect via wifi, though the mentioned bug forces me to turn wifi off and on after every reboot. With wifi working i can access via ssh and samba, so i got my games on the pi by now, but i can't get a connection to the webinterface.
Also to me the systems seems very slow, sometimes i wait for a minute after clicking on network for example.Hope you may have some suggetions for these effects.
Thank you.
-
@oluminion should be fixed with today release (i hope). Download straight rhe img at archive.recalbox.com
-
@Substring
Thank you for the info. Seems to be working fine for the wifi part, so now everything is fine except that i can't connect to the webinterface. It is enabled in the conf, but neither by ip nor by http://recalbox i get an connection.Any idea on how to fix the last problem?
Thank you very much.
-
@oluminion try with your recalbox IP
-
@substring
Neither connection method works ip nor http://recalbox -
@oluminion i guess there is something wrong in your router or network setup ... You could eventually locally log on recalbox with a keyboard (F4 to exit ES, CTRL+ALT+F2 to reach a terminal) and try to ping all those other network devices.
-
@substring
I ssh'd into recalbox and pinged the router aswell as the pc i am trying to reach the webinterface from and both pings worked without any packet loss -
@oluminion is the manager started at least ???
-
@substring
How do i check that? -
@oluminion run
ps -ef | grep node | grep "dist/server.js"
-
@substring said in Can't connect to Recalbox:
ps -ef | grep node | grep "dist/server.js"
ps -ef | grep node | grep "dist/server.js"
No output so i guess it is not running. But the recalbox.conf is still in standard config:
Recalbox Manager (http manager)
system.manager.enabled=1
1 or 2, depending on the manager version you wish
system.manager.version=2
So what can the cause be?
Thank you very much for your patience.
-
I had yesterday a similar problem after 18.07.13 update, but my problem was only with the ssh connection. After rebooting several times and checking everything, the only thing that actually helped was to shutdown the router and turn it on again (in my case, I waited 10 seconds). Only after that, ssh was working.
-
@oluminion set the manaver to version 2, make sure it's started in the advanced settings in es