RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    No longer able to autoboot to ES after VPN/Transmission init script.

    Scheduled Pinned Locked Moved Help and Support
    autostartemultionstationvpntransmission
    9 Posts 2 Posters 1.3k Views
    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.
    • G
      gdallas
      last edited by

      Pi Model - Raspberry Pi 3 Model B Quad Core CPU 1.2 GHz 1 GB RAM
      Power Supply used: powered from NAS USB
      RetroPie Version Used - unsure how to check. sorry.
      Error messages received: none. just cant boot into ES.

      Guide used: https://www.htpcguides.com/remote-access-transmission-torrent-behind-vpn-linux/

      Hello. I can no longer use ES since following this guide, which I followed to allow remote Transmission Daemon access to my PI when using my VPN. This guide worked a treat, however my PI no longer boots into ES. instead the last row of text i see on my screen is

      'Initialization Sequence Completed'

      pressumably talking about by VPN setup.

      any ideas how i get it to carry on loading all ES etc?

      Many thanks
      G

      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @gdallas
        last edited by mitu

        @gdallas What happens if you log in and start Emulationstation manually, by typing emulationstation at the command prompt.
        EDIT: You can try to use the RetroPie-Setup script and choose the autostart module to disable and then enable the autostart on boot, also choosing Emulationstation to be started on boot.

        1 Reply Last reply Reply Quote 0
        • G
          gdallas
          last edited by

          @mitu said in No longer able to autoboot to ES after VPN/Transmission init script.:

          RetroPie-Setup script

          so from Putty I can SSH 'emulationstation' and it loads ok. but as soon as i close putty it goes back to the same screen with init seq completed etc.

          I have this code for my VPN that runs from /etc/rc.local. I tried adding emulationstation in there too but didnt load.

          sleep 10
          cd /etc/openvpn
          sudo openvpn --config /etc/openvpn/ipvanish-UK-Manchester-man-c06.ovpn --auth-user-pass /etc/openvpn/login.txt --script-security 2 --up /etc/openvpn/torrentvpn.sh --do$

          sleep 3
          emulationstation

          exit 0

          mituM 1 Reply Last reply Reply Quote 0
          • mituM
            mitu Global Moderator @gdallas
            last edited by

            @gdallas You shouldn't load ES from the same script as the VPN. Use the RetroPie setup script as I mentioned and see if it auto-loads at start after you re-configure the boot/start options.

            1 Reply Last reply Reply Quote 0
            • G
              gdallas
              last edited by

              ye I only just tried that there to check. was clutching at straws. Wasnt there when i posted. So i went into the RP setup script and done what you said. I got confirmation that ES would start at boot. but it didnt.

              mituM 1 Reply Last reply Reply Quote 0
              • mituM
                mitu Global Moderator @gdallas
                last edited by mitu

                @gdallas Modify the contents of /etc/rc.local and put an & (ampersand) at the end of the line with the openvpn command:

                sudo openvpn --config /etc/openvpn/whatever.ovpn --auth-user-pass /etc/openvpn/login.txt --script-security 2 --up /etc/openvpn/torrentvpn.sh --down /etc/openvpn/torrentvpnstop.sh
                
                

                should be

                openvpn --config /etc/openvpn/whatever.ovpn --auth-user-pass /etc/openvpn/login.txt --script-security 2 --up /etc/openvpn/torrentvpn.sh --down /etc/openvpn/torrentvpnstop.sh &
                

                You don't need sudo, since the script is already started as root.

                EDIT: replace the whatever.ovpn in the example command lines above with the actual filename you configured.

                1 Reply Last reply Reply Quote 0
                • G
                  gdallas
                  last edited by

                  Excellent, that seemed to work. Thanks mitu. I presume the issue was i just didnt copy the full code from that guide then?

                  mituM 1 Reply Last reply Reply Quote 0
                  • mituM
                    mitu Global Moderator @gdallas
                    last edited by

                    @gdallas said in No longer able to autoboot to ES after VPN/Transmission init script.:

                    I presume the issue was i just didnt copy the full code from that guide then?

                    The original tutorial you linked didn't have the modification I mentioned, so the tutorial itself has the error. They should mention that the auto-start block added in /etc/rc.local blocks the boot sequence.

                    1 Reply Last reply Reply Quote 1
                    • G
                      gdallas
                      last edited by

                      Genius . Thank you very much. very happy now :-)

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

                      Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                      Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.