https://prefect.io logo
Title
d

David Mannion

02/01/2022, 9:36 PM
Hi all, I'm looking to get started with Prefect. I've installed Prefect Server on an EC2 instance in a private subnet which I can access via a bastion server. I've successfully started the server and can see it running. I'm trying to access the ui by using a putty tunnel to forward a port on my laptop, via the bastion server, to the <machine with prefect>:8080. I configured firefox to use SOCKS5 with localhost and the port forwarded by putty. Unfortunately I'm not getting the ui to load up. It's a difficult one to debug as there's lots of components involved. Has anyone any experience doing something like this? Any tips on prefect configuration that might be pertinent?
k

Kevin Kho

02/01/2022, 9:37 PM
Did you use helm or just the
prefect server start
?
d

David Mannion

02/01/2022, 9:49 PM
I'm not using helm no
k

Kevin Kho

02/01/2022, 9:53 PM
Did you start with the
--expose
flag? The warning seen here a bit below
d

David Mannion

02/01/2022, 9:54 PM
yes tried with and without the --expose flag
k

Kevin Kho

02/01/2022, 10:00 PM
That would be the only relevant config. Kinda hard to way what is going on. If you could try accessing the UI or graphQL endpoint from the same EC2 just to confirm it’s working, that would help. If it is, then it’s really all networking and that’s a bit too deep for us to dive into
d

David Mannion

02/01/2022, 10:10 PM
ok yeah I can see the heartbeat ticking away getting status 200 responses on the EC2 so looks like it is working. I was thinking there might be something in the config.toml to adjust.
k

Kevin Kho

02/01/2022, 11:39 PM
Other than pointing the UI to the graphQL endpoint, nothing else I think
g

Greg Sharples

02/03/2022, 11:17 AM
HI @David Mannion I'm having a similar issue at the moment. I can actually see the UI, but can't then connect to apollo when I'm following the
/getting-started
route. Have you managed to make any further progress?
d

David Mannion

02/03/2022, 11:22 AM
Hi Greg, no not yet. I'm waiting on port 8080 to be opened on the EC2 instance so still haven't reached the ui.
g

Greg Sharples

02/03/2022, 11:23 AM
Ah ok good luck! I'll keep trying to figure this out so give me a shout if you run into similar problems!
d

David Mannion

02/03/2022, 11:24 AM
will do thanks!
g

Greg Sharples

02/03/2022, 11:51 AM
@Kevin Kho hoping you could help here - as well as opening port 8080 am I right in thinking we also need to open 4200 so we can send requests to the graphql service separately from the ui?
I've answered my own question ^^^. One to be aware of @David Mannion
d

David Mannion

02/03/2022, 11:58 AM
thanks for the heads up, will add 4200 to my ticket
k

Kevin Kho

02/03/2022, 2:57 PM
Yes. From this blog:
You'll also want to add firewall rules for the GraphQL server (port 4200) and the UI (port 8080), so your firewall rules page will look something like...
🙌 1