am i missing something

Question

josh · Answer

Hey < Nazeer Hussain> someone opened an issue which I think is related here They ended up pruning their docker system and it appears to have worked This seems to be due to docker s default caching semantics

Nazeer Hussain · Answer

Thanks < josh> let me check

Nazeer Hussain · Answer

Unfortunately this did not work

nicholas · Answer

Hi < Nazeer Hussain> what does your `config toml` file contain

Nazeer Hussain · Answer

let me get that one moment plz

Nazeer Hussain · Answer

backend = server server host = port = 4200 host port = 4200 endpoint = $ server host $ server port server graphql host = server ui host = port = 8081 host port = 8081 endpoint = $ server ui host $ server ui port graphql url =

Nazeer Hussain · Answer

oh i think i made a mistake

Nazeer Hussain · Answer

just give me a moment please

Nazeer Hussain · Answer

< nicholas>

Nazeer Hussain · Answer

ec2 user ip 172 31 1 219 ~ $ cat prefect config toml backend = server server host = port = 4200 host port = 4200 endpoint = $ server host $ server port server graphql host = server ui host = port = 8080 host port = 8080 endpoint = $ server ui host $ server ui port graphql url =

Nazeer Hussain · Answer

i changed the port to 8080

Nazeer Hussain · Answer

but still i am unable to access the Prefect UI at <http prefect naazit com 8080 >

Nazeer Hussain · Answer

in the prefect start server it shows this log scheduler 1 | 2020 06 12 15 00 47 662 INFO prefect server Scheduler | Scheduled 0 flow runs scheduler 1 | 2020 06 12 15 00 47 763 DEBUG prefect server Scheduler | Sleeping for 300 0 seconds ui 1 | var www js welcome df9a970c js ui 1 | space invader space invader space invader UI running at localhost 8080 space invader space invader space invader

Nazeer Hussain · Answer

UI running at localhost 8080

nicholas · Answer

< Nazeer Hussain> the `prefect server start` only runs a local version of the Prefect application You ll need to configure your own webserver to route external traffic to the application In this case you could use something like `nginx` s proxypass to serve traffic to localhost 4200 and localhost 8080

Nazeer Hussain · Answer

ok let me try that < nicholas> thank you i will get back to you shortly

Nazeer Hussain · Answer

so I need to remove the config toml

Nazeer Hussain · Answer

and just handle it with nginx

nicholas · Answer

I misspoke there my apologies since you re trying to access the ports directly on the machine you shouldn t need to use a webserver you will need to configure your DNS records to route to that which I m assuming you ve already done and you ll need to open up those ports on your machine to external traffic

Nazeer Hussain · Answer

I am doing this on AWS EC2 instance on Amazon Linux

Nazeer Hussain · Answer

So i assume i will run the prefect locally and handle the reverse proxy via nginx

Nazeer Hussain · Answer

is that a fair understanding

nicholas · Answer

Hm I m not sure When I say locally I mean local to the machine where you re deploying the application

nicholas · Answer

You re running `prefect server start` on your ec2 correct

Nazeer Hussain · Answer

yes

Nazeer Hussain · Answer

thats right

Nazeer Hussain · Answer

so should i remove the config toml altogether and go with the default ports and config of prefect

nicholas · Answer

Ok great Then you need to open ports 4200 and 8080 on the machine you can do this through the AWS Console

Nazeer Hussain · Answer

Yes i did that in the Security groups

nicholas · Answer

Can you access the UI at your machine s public IP address at port 8080

Nazeer Hussain · Answer

yes public IP it works except the API status issue with graphql

Nazeer Hussain · Answer

let me get that URL

Nazeer Hussain · Answer

i will erase the config file and spin up in a min

nicholas · Answer

We ll need to add the config again but it ll be good to start with a fresh one

Nazeer Hussain · Answer

Nazeer Hussain · Answer

you can see that the API status is still down disappointed

Nazeer Hussain · Answer

let me erase the config toml from prefect config toml and configure the nginx

nicholas · Answer

Hold on

Nazeer Hussain · Answer

ok

Nazeer Hussain · Answer

i am listening

nicholas · Answer

I don t think this has anything to do with the API or the prefect installation

Nazeer Hussain · Answer

ok

nicholas · Answer

Your domain doesn t seem to be configured to route traffic to that IP address

Nazeer Hussain · Answer

ok probably I will do the nginx and test

Nazeer Hussain · Answer

it might be the issue

nicholas · Answer

Ok sure it s possible the machine isn t configured to receive that traffic on localhost

Nazeer Hussain · Answer

ok got it i am fixing slightly smiling face

Soham · Answer

just curious were you able to fix this Nazeer i m having literally the sample problem trying to deploy this on an ec2 would love to know if you were able to solve

Soham · Answer

i m also seeing the same API status error

Soham · Answer

update everything seemed to start working fine once i registered a flow

Soham · Answer

i m trying on a separate server today and the problem seems to be back so < Nazeer Hussain> do lmk if you found some solution thanks

Nazeer Hussain · Answer

Nope < Soham> same issue persists i tried everything will keep you posted