![]() Logged right in, claimed the server for the account, it popped right up on my other devices. Just wait.įirefox popped up after a minute, accessed Plex via: It always takes a while to open, but it's usually functional when it opens. Then ran Firefox from the plex server, locally firefox Installed a web browser with: sudo apt install firefox So I SSH 'd into my Ubuntu Plex server with the -X flag (allows GUI apps to be displayed on a local Linux machine, from the remote machine). I had also logged into the server with a browser on the same network by IP, still wouldn't claim it. I had checked the local IP rage, and that was correct, so that work around that others had luck with, wouldn't help me. Then I remembered that SSH allows "X over SSH" and that was probably the easiest way to get up and running. So connecting a monitor isn't an option (or, it won't help any more than the SSH access I already had). Like many, I was able to log back into my devices, but the server wouldn't let me claim it (and I'm not sure if it even got the server logged back in at all). Pre-up iptables-restore < /etc/lesÄone! Feel free to leave a comment with your questions or suggestions.When I changed my password, it had it log everything out, and didn't think about that including my server. Sudo iptables -A INPUT -p tcp -dport 32400 -j DROP Only allow local connections to port 32400 sudo iptables -A INPUT -p tcp -s localhost -dport 32400 -j ACCEPT Plex.TV Web App > Settings > Server > Network > Custom server access URLs 6. Go to on your browser, if it does not load the tunnel was not setup correctly 5. Loaded: loaded (/etc/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Mon 03:11:14 CET 2 days agoĬGroup: /system.slice/rvice ![]() If tunnel was created successfully output should look something like this: rvice - AutoSSH tunnel service Plex on local port 32400 Check SSH tunnel sudo systemctl status autossh-plex-tunnel Create systemd service file sudo nano /etc/systemd/system/rviceÄescription=AutoSSH tunnel service Plex on local port 32400Ä®xecStart=/usr/bin/autossh -M 40584 -o "compression=no" -o -o "ServerAliveInterval 30" -o "ServerAliveCountMax 3" -NR 32400:localhost:32400 Enable and start service sudo systemctl enable autossh-plex-tunnelĤb. Install autossh sudo apt install autosshÄ£b. Install autossh and create systemd service:Ä£a. Add "Gatewayports yes" to sshd_config nano /etc/ssh/sshd_configÄ¢b. Edit tunnel's SSH server configurationÄ¢a. Last login: Wed Feb 22 03:49:58 should not be promted for a password 2. Now try logging into the machine, with: "ssh check to make sure that only the key(s) you wanted were added.Ä¡c. Reinstall the Plex container by running the following command: sb install plex Using SSH Tunneling to log into Plex and set your credentials: On your host PC (replace with your user name and with your serveripaddress - no arrows): ssh -L 32400:0.0.0.usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed - if you are prompted now it is to install the new password: Copy SSH key ssh-copy-id INFO: attempting to log in with the new key(s), to filter out any that are already installed Passaphrase must be empy for autossh to work!Ä¡b. Your public key has been saved in /root/.ssh/id_rsa.pub. Your identification has been saved in /root/.ssh/id_rsa. Setup SSH keys (if you already have key based authenthication setup skip to step 2)Ä®nter file in which to save the key (/root/.ssh/id_rsa):Ä®nter passphrase (empty for no passphrase): Step 2 is done on the tunnel, all other steps are done on the plex server. This guide creates a reverse SSH tunnel to route all Plex server traffic through it. ![]() Routing plex traffic through an SSH tunnel Replace localhost with the plex hostname or its ip.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |