Solved Netzwerkproblem

[lackyluuk]

@Spectral_PS4 please provide your discoveries to @Substring in english

It looks that recalbox.com can be pinged.

[Spectral_PS4]

@Substring I have exactly the same problem. Wanted yesterday from the beta to the final update. I am also displayed after the start, which is an update is available, but I can not download it, because supposedly no network connection exists. Racalbox can be ping and can be accessed via the browser. A restart of the router (Fritz! Box) has not fixed the error.

[Substring]

@Spectral_PS4 you can't download the update ? What's the error message ?

[Spectral_PS4]

@Substring The error message is "No network connection". I can ping Recalbox and the system is accessible via Samba. The update I then executed manually, the error persists. See also Forum Post by seic

[seic]

@Substring
It gives you the message that there is no connection if you want to update via Recalbox OS.
But the strange thing is I can scrape roms even if the OS shows me no connection.

[Substring]

@seic That's either a DNS problemeither a scripting error to detect the internet connection. We're digging into the problem

[Substring]

So, recalbox pings recalbox.com to check if you're "connected". That DNS is irrevelant as not everyone can ping it, may correct that

[Mischler81]

I have the same problem and I also live in Germany.

I can't ping recalbox.com from any device in my network. The ip adress ist found but the server doesn't respond.

I'm still using Beta 6 of recalbox and updating is not possible at the moment.

[DannyOcean]

Same problem, also from Germany.
Settings show "no connection". Connection via SSH is fine.

Strange thing is that scraping of ROMs works and tracking with retroachievements server also work as it should. But no updates possible.

Yes, w-lan settings are correct, also looked in the config.

[DannyOcean]

@Substring said in Netzwerkproblem:

So, recalbox pings recalbox.com to check if you're "connected". That DNS is irrevelant as not everyone can ping it, may correct that

I can ping WWW.recalbox.com but not recalbox.com

The "www" has to be in the address

[DannyOcean]

@Nachtgarm @paradadf @lackyluuk @Substring

Das Problem, dass recalbox.com nur mit 'www' vorne dran erreichbar ist, besteht weiterhin.

Wie ist denn die recalbox Domain in ISPConfig angelegt (mit www oder ohne)?
Diese muss ohne www, also nur 'RECALBOX.DE' angelegt sein und dann 'www' als Auto-Subdomain ausgewählt sein.

Macht mal eine nslookup für RECALBOX.DE

und für WWW.RECALBOX.DE

und kontrolliert welche IPs zurück gegeben werden. Die IPs müssen identisch sein.

If your host (gandi.net ?) supports .htaccess there might be an easy solution.

EDIT:
IP for www.recalbox.com is 163.172.153.70
IP for recalbox.com is 217.70.184.38

That is why the update is not working and the recalbox shows "not connected"

[Substring]

@DannyOcean still, some people can ping recalbox.com, some others can't. We're working on it

[DannyOcean]

@Substring
sure, but to fix the problem the IP for recalbox.com and www.recalbox.com just have to be the same.
Check the DNS settings and see the A record for yourself.
The hoster (gandi.net ?) should be able to fix it.

In ISPconfig the domain has to be "RECALBOX.COM" (without www) and auto-subdomain has to be "www"

The A records in the DNS setting:
IP for www.recalbox.com is 163.172.153.70
IP for recalbox.com is 217.70.184.38

That is why the update is not working and the recalbox shows "not connected"

To fix the problem the IP for recalbox.com and www.recalbox.com just have to be the same.
Check the DNS settings and see the A record for yourself.
The hoster (gandi.net ?) should be able to fix it.

You also have to add the following code to your root .htaccess file:

This redirects all non-www requests to your site to the www version

RewriteEngine on
RewriteCond %{HTTP_HOST} !^www.
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]

The second line means: if the HTTP_HOST does not (!) start with (^) "www.", then put it in memory for the next line. The next line says: from what was captured in the previous line, match everything (.*) from beginning (^) to end ($) and save everything (inside the parenthesis) as $1. Then replace $1 with ""; plus the HTTP_HOST variable.

And this would redirect all www requests to your site to the non-www version
RewriteEngine On
RewriteCond %{HTTP_HOST} !^my-domain.com$ [NC]
RewriteRule ^(.*)$ http://my-domain.com/$1 [R=301,L]

I really hope this helps, and everyone will be able to update

Cheers

[Substring]

@DannyOcean @digitaLumberjack is in charge of all that, i don't manage DNS stuff

[DannyOcean]

Cool, es scheint nun gelöst zu sein
GEILE TYPEN

[Nachtgarm]

Immer gerne

[chriz]

Hallo,
vielen Dank für die ganze Hilfe hier im Forum!
Bei mir klappt das leider immer noch nicht - wie kann ich das Problem nun lösen? das posting von DannyOcean hilft mir leider nicht weiter, weil ich nicht verstehen was ich wo einstellen/konfigurieren muss.
Der RasPi bekommt die IP von meiner FritzBox, der DNS-Server kommt von Unitymedia

[morphus]

Hallo zusammen,

ich kämpfe auch verzweifelt mit diesem Problem...
Kennt jemand einen DNS Server der "recalbox.com" auflösen kann?
Die HOSTS Datei auf dem OS kann man ja leider nicht editieren (oder hat jemand nen tipp wie) und ich kriege keinen lokalen DNS hin um es zu umgehen

[Substring]

SOLUTION UNTIL IT IS FIXED UPSTREAM :
edit ~/.emulationstation/es_settings.cfg and replace <string name="UpdateServer" value="recalbox.com" /> with <string name="UpdateServer" value="archive.recalbox.com" />

[chriz]

Hi,
leider funktioniert die vorgeschlagene Lösung von substring nicht.
Wenn ich die settings.cfg über den PC via Netzwerk editiere und abspeichere (Win10 greift über den Dateiexplorer auf die IP von RecalBox zu, editiert wird mit Notepad++), dauert es nur wenige Sekunden bis (irgendwas im Hintergrund) den Originaleintrag wiederherstellt.

Hi,
unfortunately it doesn't work
When I edit settings.cfg (of course with saving!) few seconds later the original entry (value="recalbox.com") will be rewrite from recalbox. So I think i'll waiting till the recalbox-IP is fixed...