New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Plex initial setup
If anyone is a plex guru, maybe you can help me out.
I've got a clean plex install on a headless Linux server, and to complete the setup I need to connect to localhost:32400 via browser to claim it. I know I can do a ssh tunnel to accomplish this, but is there a way to do this via a direct http or https connection to the public IP address?
I've tried doing a reverse proxy but that only works after the server is already claimed, not when it's a clean install.
Any input is greatly appreciated!
Comments
not the most secure method but its probably fine for short term setup like this:
https://www.digitalocean.com/community/tutorials/how-to-set-up-vnc-server-on-debian-8
I use x2go if I need gui access as its secure but its setup is a bit more complex: http://www.tecmint.com/setup-remote-desktop-using-x2go-server-and-client-in-debian/
Haproxy in front
I assume the reverse proxy doesn't work because you're not showing as coming from the IP it wants to see; can you not just hardcode the relevant header in your proxy config for 5 minutes whilst you claim the server?
Might be a way to do this va hacking a config file. There's an option in the admin panel where you can whitelist certain IPs for passthrough access to admin, maybe there's a way to set these in a static config file?
Why can't you just use the ssh tunnel? Takes but a minute or two and wouldn't require you to install any additional packages or mess with configs.
https://blog.vpetkov.net/2015/12/17/plex-server-on-a-vps-docker-setup-without-port-forwarding/
The quickest and easiest way is to just use the SSH tunnel.
@RXWatcher Thanks for the suggestion.
@reetwood I just tried haproxy and it is doing the same thing that apache reverse proxy does, i.e. plex still doesnt see this as a local connection. any suggestions on the haproxy config I'm missing?
@Nekki this is exactly what I'm trying to do, but I'm not sure how to accomplish this without the ssh tunnel.
@Harambe There is a setting under the server -> network that allows you enter IP for no auth, but this doesn't work when I enter the public IP of the vps.
@MasonR I can and do use this method, however, when setting up boxes for friends/family I would like for them to connect directly via a web-browser instead of teaching them how to use putty to make ssh tunnels
@yolo_me I looked at this but it may a bit over my head. I already have a vps setup with plex installed. I just want to be able to trick plex into thinking that I'm connected locally to setup my server instead of remotely.
So in summary: after installing plex, I want to connect via http/https public ip to finish the setup and claim the server.
If anyone else has got this to work please let me know!
@vish you need to follow the link I set up. I encountered your problem before and that solved it. Just find the Preferences.xml with
find / -name 'Preferences.xml'
paste the PlexOnlineToken from google chrome and that's it. Your call if you wanna make this happen.
Also, I don't understand why you can't do SSH port forwarding. It's literally one command line and you're done.
I explained what to do. You need to the appropriate header so your proxy reports that you're coming from whatever location Plex is happy with, presumably 127.0.0.1.
https://www.ssh.com/ssh/tunneling/example
http://blog.trackets.com/2014/05/17/ssh-tunnel-local-and-remote-port-forwarding-explained-with-examples.html
lmgtfy
Why not squid proxy?
It work just fine for me with rclone.
Ssh tunnel
The first link straightened me out. Feel really stupid now. I guess I didn't realize I can create local ssh tunnels.
Every time one of you guys said ssh tunnel, I immediately thought remote ssh tunnel in the putty flavor.
DOH!
Thanks again
ssh -NL 32400:localhost:32400 user@host
- browse to localhost:32400 on your local machine and it's tunnelling that traffic to localhost:32400 on the server. Wham bam thank you mam.EXAMPLE: curl -H "host: 127.0.0.1" http://the_remoteip:whatevverport
so in chrome/firefox get a plugin that can change your headers and do that.
nothing you need to configure in ssh/haproxy/apahce