I'm trying to set up a Plex media server on an EC2 instance, and while I've got it running, I'm facing an issue when trying to log in—it says the user is not authenticated. I'm also having trouble connecting via SSH because I'm receiving an error saying my .pem file is too public. I thought I had it shared only with my account and the system. What steps can I take to resolve these issues?
3 Answers
Make sure your .pem file can only be read by you. On Linux or Mac, run `chmod 400 ` in the terminal. For Windows, right-click the file, go to Properties, and adjust the permissions accordingly. It’s all about keeping it secure from public access!
If this is giving you trouble, maybe AWS isn't the best choice for you right now. You could end up more confused later on! Just remember, to fix the 'too public' issue, change the permissions of your SSH key to '400'. The official documentation explains this too, so check that if you need more info.
Yeah, and just wait till your next post is about AWS charging you a fortune! It's definitely a learning curve, so take it slow and you'll get the hang of it.
Setting up Plex on EC2 can be tricky if you're not familiar with SSH and file permissions. Just a heads up, running Plex requires a decent amount of hardware for transcoding, so be prepared for potential costs. If you're looking for a budget option, a VPS host might be a better fit for you!
I totally get that, but remember, this is a university project, right? So if cost is a concern, sticking with the free tier is a smart move. You can manage your server without those extra expenses and it's only temporary until you get your grade!
Exactly! This is more of a security issue rather than an AWS problem. Just ensure your SSH key permissions are correctly set, and you should be good to go!