Recalbox Forum

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • recalbox.com
    • Gitlab repository
    • Documentation
    • Discord

    Solved Can't Connect

    Recalbox General
    cant connect
    11
    47
    24370
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Substring
      Substring @mazur last edited by

      @mazur as i said : check your DNS and gateway on recalbox, and what happens on your router. If you set a static ip'on recalbox, you may have forgotten what i said

      Former dev - Please reply with @substring so that i am notified when you answer me
      Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

      1 Reply Last reply Reply Quote 0
      • mazur
        mazur last edited by

        Already check everything.. dunno what to do 😞

        Substring 1 Reply Last reply Reply Quote 0
        • Substring
          Substring @mazur last edited by

          @mazur cdan you paste the result of ifconfig? and route or route print ?

          Former dev - Please reply with @substring so that i am notified when you answer me
          Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

          mazur 1 Reply Last reply Reply Quote 0
          • mazur
            mazur @Substring last edited by Nachtgarm

            @Substring , please check:

            # ifconfig
            eth0      Link encap:Ethernet  HWaddr B8:27:EB:79:9E:06
                      inet addr:192.168.25.4  Bcast:192.168.25.255  Mask:255.255.255.0
                      inet6 addr: fe80::ba27:ebff:fe79:9e06%1994427092/64 Scope:Link
                      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                      RX packets:158 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:163 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:1000
                      RX bytes:15499 (15.1 KiB)  TX bytes:24591 (24.0 KiB)
            
            lo        Link encap:Local Loopback
                      inet addr:127.0.0.1  Mask:255.0.0.0
                      inet6 addr: ::1%1994427092/128 Scope:Host
                      UP LOOPBACK RUNNING  MTU:65536  Metric:1
                      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                      collisions:0 txqueuelen:0
                      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
            
            #
            
            # route
            Kernel IP routing table
            Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
            default         192.168.25.1    0.0.0.0         UG    0      0        0 eth0
            192.168.25.0    *               255.255.255.0   U     0      0        0 eth0
            #
            
            # /etc/resolv.conf
            search domain.name # eth0
            nameserver 192.168.25.1 # eth0
            
            # /etc/network/interfaces
            
            auto lo
            iface lo inet loopback
            
            auto eth0
            iface eth0 inet dhcp
            
            auto wlan0
            iface wlan0 inet dhcp
            wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
            
            
            # ping recalbox.com
            PING recalbox.com (217.70.184.38): 56 data bytes
            --- recalbox.com ping statistics ---
            75 packets transmitted, 0 packets received, 100% packet loss
            

            I changed resolv.conf and interfaces but that files keeping returning to the default DHCP settings, already tryed to make them readonly, no sucess..

            1 Reply Last reply Reply Quote 0
            • Substring
              Substring last edited by

              Have you tried pinging google rather ?

              Former dev - Please reply with @substring so that i am notified when you answer me
              Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

              mazur 1 Reply Last reply Reply Quote 0
              • mazur
                mazur @Substring last edited by

                @Substring Yes, pinging any other site works..

                Substring 1 Reply Last reply Reply Quote 0
                • Substring
                  Substring @mazur last edited by

                  @mazur ok can you try a traceroute to recalbox.com, archive.recalbox.com and www.recalbox.com ? Thank you

                  Former dev - Please reply with @substring so that i am notified when you answer me
                  Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                  CapFuture1975 1 Reply Last reply Reply Quote 0
                  • CapFuture1975
                    CapFuture1975 @Substring last edited by

                    When i use my pc with firefox, i also get a timeout error to connect to recalbox.com sever.

                    1 Reply Last reply Reply Quote 0
                    • Substring
                      Substring last edited by Substring

                      recalbox.com itself means nothing, should try with www.recalbox.com. And as your are on the forum, i guess the DNS does work

                      ooops it does work for me :

                      # ping recalbox.com
                      PING recalbox.com (217.70.184.38): 56 data bytes
                      64 bytes from 217.70.184.38: seq=0 ttl=53 time=7.614 ms
                      64 bytes from 217.70.184.38: seq=1 ttl=53 time=7.370 ms
                      64 bytes from 217.70.184.38: seq=2 ttl=53 time=7.448 ms
                      64 bytes from 217.70.184.38: seq=3 ttl=53 time=7.336 ms
                      64 bytes from 217.70.184.38: seq=4 ttl=53 time=7.521 ms
                      64 bytes from 217.70.184.38: seq=5 ttl=53 time=7.438 ms
                      64 bytes from 217.70.184.38: seq=6 ttl=53 time=7.607 ms
                      64 bytes from 217.70.184.38: seq=7 ttl=53 time=7.504 ms
                      ^C
                      --- recalbox.com ping statistics ---
                      8 packets transmitted, 8 packets received, 0% packet loss
                      round-trip min/avg/max = 7.336/7.479/7.614 ms
                      

                      Former dev - Please reply with @substring so that i am notified when you answer me
                      Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                      1 Reply Last reply Reply Quote 0
                      • Substring
                        Substring last edited by Substring

                        try pinging www.recalbox.com instead please

                        Former dev - Please reply with @substring so that i am notified when you answer me
                        Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                        1 Reply Last reply Reply Quote 0
                        • Substring
                          Substring last edited by

                          Been searching : it pings recalbox.com to say if you're connected or not. I guess we'll change that in 4.1 as this DNS is not accurate and points to nothing special. So the message NOT CONNECTED is a mistake

                          Former dev - Please reply with @substring so that i am notified when you answer me
                          Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                          mazur DannyOcean 2 Replies Last reply Reply Quote 0
                          • mazur
                            mazur @Substring last edited by

                            @Substring Thanks very much!

                            1 Reply Last reply Reply Quote 0
                            • DannyOcean
                              DannyOcean @Substring last edited by

                              @Substring

                              Same problem.
                              Network settings show "not connected".
                              But 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.
                              I can ping WWW.recalbox.com but not recalbox.com - same with firefox via laptop.

                              recalbox pings recalbox.com to check if we're "connected".

                              The "www" has to be in the address.

                              So how do we update to 4.1 if we get no connection with 4.0?

                              Substring 1 Reply Last reply Reply Quote 0
                              • Substring
                                Substring @DannyOcean last edited by

                                @DannyOcean easy pal ...

                                4.1 is not here, we are taking care of that dns thing. We'd still have a few tricks up our sleeve anyway. I'd like to say it should be solved by the weekend as we're working on it, but it does not only depend on us

                                Former dev - Please reply with @substring so that i am notified when you answer me
                                Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                                DannyOcean 1 Reply Last reply Reply Quote 0
                                • DannyOcean
                                  DannyOcean @Substring last edited by DannyOcean

                                  @Substring always easy 🙂
                                  Also wanted to say a big THANK YOU to you and your colleagues. Coders, forum admins, translators etc... 🙂

                                  1 Reply Last reply Reply Quote 0
                                  • DannyOcean
                                    DannyOcean last edited by

                                    blog.recalbox.com also not working.

                                    forum.recalbox.com is fine ... strange

                                    1 Reply Last reply Reply Quote 0
                                    • Substring
                                      Substring last edited by

                                      the blog is dead for months already

                                      Former dev - Please reply with @substring so that i am notified when you answer me
                                      Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                                      1 Reply Last reply Reply Quote 0
                                      • DannyOcean
                                        DannyOcean last edited by

                                        @digitaLumberjack @Substring

                                        Sorry for double post, but I wanted to let you know that there might be an easy solution to fix the "no connection" problem.

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

                                        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

                                        fegemo 1 Reply Last reply Reply Quote 1
                                        • fegemo
                                          fegemo @DannyOcean last edited by

                                          I am having the exact same issue - emulationstation does not recognize it's connected because the ping to recalbox.com fails. But kodi works fine.

                                          Any updates on this?

                                          Thanks!!!

                                          mazur 1 Reply Last reply Reply Quote 0
                                          • mazur
                                            mazur @fegemo last edited by

                                            @fegemo Not yet.. Waiting for 4.1 version..

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Want to support us ?

                                            73
                                            Online

                                            99.6k
                                            Users

                                            28.1k
                                            Topics

                                            187.1k
                                            Posts

                                            Copyright © 2021 recalbox.com