I have my Plex server setup on one of my 64 GiB memory dedicated servers in the AWS cloud. I am an experienced network engineer and I am connecting directly to the VPC (Virtual Private Cloud) that the server is on. I can access the web server through both it’s public I.P and its local IP (when connected to the VPC). So why is it that the server cannot find itself, and there was absolutely zero initial setup wizard? I would love to use Plex as opposed to my Amazon system, but at this point AWS is being easier to work with than this software…
SSH tunnel to the remote system mapping 8888 to remote 32400
Access locally as 127.0.0.1:8888/web
Elaborate. I am an AWS Engineer but really don’t know my way around linux.
e> @mgballew said:
I have my Plex server setup on one of my 64 GiB memory dedicated servers in the AWS cloud. I am an experienced network engineer and I am connecting directly to the VPC (Virtual Private Cloud) that the server is on. I can access the web server through both it’s public I.P and its local IP (when connected to the VPC). So why is it that the server cannot find itself, and there was absolutely zero initial setup wizard? I would love to use Plex as opposed to my Amazon system, but at this point AWS is being easier to work with than this software…
Please elaborate and explain your credentials. If you’re a network engineer, surely you understand tunneling ?
The AWS system is Linux AFAIK.
I am an AWS Network Engineer/Consultant. I setup Virtual Private Clouds, then configure the private/public subnets, make sure the routing tables and ACLs are all in order with the companies specs, then connect the entire network to theirs via VPN. Its a complicated process but I work with a team who handle the details of each connection, I more of a broader picture kind of guy. Very rarely do I actually interact with any terminal, and I literally just discovered that I had this dedicated server still running the other day and wanted to use it for stuff. I just am not great with linux. Of course I understand tunneling Its been so long though.
To clarify?
You’re experienced in setting up machines operating Amazon’s web interface to setup server instances ?
I believe this is the proper support article for you to read.
Lol buddy, come on.
Yeah I know my way around linux and yes I am experienced launching all kinds of instances in EC2 etc etc. I am tunneling to the server with Putty and what can I say…its not working. Here’s everything I know.
Server’s internal address: 15.15.15.186
Subnet configuration: public
Firewall: wide open
I can connect to the local VPN server and go to 15.15.15.186:3400/web without any problems. No initial setup wizard or anything like that though.
Same story for the public IP. Is there something i have missed or am I correct in that the server for some reason skipped the initial setup wizard?
You missed the part at the end of the Installation manual On a Different Network
Respectfully, We can’t teach you Linux. Before you get too far along, maybe you would be better served with a Windows VPS?
I read the part on the “different network”. Surely they aren’t going to force you to access through localhost when remote, but not when local?
@mgballew said:
I read the part on the “different network”. Surely they aren’t going to force you to access through localhost when remote, but not when local?
I’m sure @ChuckPA will give you a much more thorough response but did you happen to read this line from the link he posted?
If you're on a different network than the server computer, you'll first need to set up a SSH tunnel so that you can access things as if they were local.
