But that can be step 2, not step 1 😄

Well, in general it's always advisable to only expose the relevant ports (i.e. 8080, 8008 and 8081).
Also, since the Trains Fileserver is not limited (i.e. no credentials are required to upload/download), we recommend only opening access from your (or your company's/office) IP, not from any IP.

alright, cracking knuckles and... dive into the deep end

I did not... 😞 I'm a bit of a newb to the EC2

so, inbound rules should allow custom TCP for the three ports, 8080, 8001, 8081? what about the outbound rules?

thank you Jake

Additionally, since you're using AWS, and assuming you have a domain name, you can fairly easily set up a Load balancer (ELB) and use subdomains instead of ports, as well as use HTTPS for safer communication 🙂

Can you open the browsers' developer panel and see what calls are being sent over the network?

Hi MinuteWalrus85 ,
Welcome 🙂
Did you make sure the new instance has a security group allowing access to port 8080? (Usually, unless otherwise configured, a new EC2 instance will only allow inbound traffic from instances in the same VPC)

now it's working!

thank you Jake for the assistance!

Well, I see you do get the favicon, so something is there... Strange

ok, so now I'm able to see the website, but the gui isn't showing up:

Oh, and another thing - if you're opening your server to outside access (and not just limited to your IP), please consider using only the fixed-users mode, so that every access to the server will be password-protected 🙂

sorry, my bad 😛 I accidentally entered into the inbound rules the port 8001 instead of 8008

I'll look at the security group. Any tips on how to configure it so that it isn't exposed to the entire world, but also not locked to me?