Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi Guys, I'M New Here

Hi guys, I'm new here 🙂 I just launched an AWS EC2 t3.large instance with the AMI from the marketplace according to the docs, and the stage of entering the URL with the http://Public DNS IPv4>:8080 does not show the web-ui

  
  
Posted 4 years ago
Votes Newest

Answers 17


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)

  
  
Posted 4 years ago

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

  
  
Posted 4 years ago

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?

  
  
Posted 4 years ago

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.

  
  
Posted 4 years ago

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 🙂

  
  
Posted 4 years ago

But that can be step 2, not step 1 😄

  
  
Posted 4 years ago

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

  
  
Posted 4 years ago

thank you Jake for the assistance!

  
  
Posted 4 years ago

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

  
  
Posted 4 years ago

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 🙂

  
  
Posted 4 years ago

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

  
  
Posted 4 years ago

image

  
  
Posted 4 years ago

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

  
  
Posted 4 years ago

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

  
  
Posted 4 years ago

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

  
  
Posted 4 years ago

now it's working!

  
  
Posted 4 years ago

thank you Jake

  
  
Posted 4 years ago