Channels
announcements
ask-marvin
best-practices-coordination-plane
data-ecosystem
data-tricks-and-tips
events
find-a-prefect-job
geo-bay-area
geo-berlin
geo-boston
geo-chicago
geo-colorado
geo-dc
geo-israel
geo-japan
geo-london
geo-nyc
geo-seattle
geo-texas
gratitude
introductions
marvin-in-the-wild
pacc-clearcover-june-12-2023
pacc-may-31-2023
ppcc-may-16-2023
prefect-ai
prefect-aws
prefect-azure
prefect-cloud
prefect-community
prefect-contributors
prefect-dbt
prefect-docker
prefect-gcp
prefect-getting-started
prefect-integrations
prefect-kubernetes
prefect-recipes
prefect-server
prefect-ui
random
show-us-what-you-got
Title
n
Nazeer Hussain
06/12/2020, 9:11 AMam i missing something
j
josh
06/12/2020, 12:57 PMHey @Nazeer Hussain someone opened an issue, which I think is related, here https://github.com/PrefectHQ/prefect/issues/2759
They ended up pruning their docker system and it appears to have worked. This seems to be due to docker’s default caching semantics
n
Nazeer Hussain
06/12/2020, 12:58 PMThanks @josh let me check
Unfortunately this did not work !!
n
nicholas
06/12/2020, 3:01 PMHi @Nazeer Hussain - what does your
config.tomln
Nazeer Hussain
06/12/2020, 3:01 PMlet me get that, one moment plz
backend = "server"
[server]
host = "http://prefect.naazit.com"
port = "4200"
host_port = "4200"
endpoint = "${server.host}:${server.port}"
[server.graphql]
host = "prefect.naazit.com"
[server.ui]
host = "http://prefect.naazit.com"
port = "8081"
host_port = "8081"
endpoint = "${server.ui.host}:${server.ui.port}"
graphql_url = "http://prefect.naazit.com:4200/graphql"
oh i think i made a mistake
just give me a moment please
@nicholas
[ec2-user@ip-172-31-1-219 ~]$ cat .prefect/config.toml
backend = "server"
[server]
host = "http://prefect.naazit.com"
port = "4200"
host_port = "4200"
endpoint = "${server.host}:${server.port}"
[server.graphql]
host = "prefect.naazit.com"
[server.ui]
host = "http://prefect.naazit.com"
port = "8080"
host_port = "8080"
endpoint = "${server.ui.host}:${server.ui.port}"
graphql_url = "http://prefect.naazit.com:4200/graphql"
i changed the port to 8080
but still i am unable to access the Prefect UI at : http://prefect.naazit.com:8080/
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 | 👾👾👾 UI running at localhost:8080 👾👾👾
UI running at localhost:8080
n
nicholas
06/12/2020, 3:13 PM@Nazeer Hussain - the
prefect server startn
Nazeer Hussain
06/12/2020, 3:14 PMok let me try that @nicholas thank you, i will get back to you shortly
so I need to remove the config.toml?
and just handle it with nginx
n
nicholas
06/12/2020, 3:17 PMI 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
n
Nazeer Hussain
06/12/2020, 3:17 PMI am doing this on AWS EC2 instance on Amazon Linux
So i assume i will run the prefect locally and handle the reverse proxy via nginx
is that a fair understanding
n
nicholas
06/12/2020, 3:19 PMHm I'm not sure. When I say locally, I mean local to the machine where you're deploying the application
You're running
prefect server startn
Nazeer Hussain
06/12/2020, 3:19 PMyes
thats right
so should i remove the config.toml altogether? and go with the default ports and config of prefect?
n
nicholas
06/12/2020, 3:20 PMOk great. Then you need to open ports 4200 and 8080 on the machine ( you can do this through the AWS Console )
n
Nazeer Hussain
06/12/2020, 3:20 PMYes, i did that in the Security groups
n
nicholas
06/12/2020, 3:20 PMCan you access the UI at your machine's public IP address at port 8080?
n
Nazeer Hussain
06/12/2020, 3:21 PMyes public IP it works, except the API status issue with graphql
let me get that URL
i will erase the config file and spin up in a min
n
nicholas
06/12/2020, 3:21 PMWe'll need to add the config again but it'll be good to start with a fresh one
n
Nazeer Hussain
06/12/2020, 3:21 PMyou can see that the API status is still down 😞
let me erase the config.toml from .prefect/config.toml and configure the nginx?
n
nicholas
06/12/2020, 3:22 PMHold on
n
Nazeer Hussain
06/12/2020, 3:22 PMok..
i am listening
n
nicholas
06/12/2020, 3:23 PMI don't think this has anything to do with the API or the prefect installation
n
Nazeer Hussain
06/12/2020, 3:23 PMok..
n
nicholas
06/12/2020, 3:23 PMYour domain doesn't seem to be configured to route traffic to that IP address
n
Nazeer Hussain
06/12/2020, 3:24 PMok probably I will do the nginx and test
it might be the issue
n
nicholas
06/12/2020, 3:25 PMOk sure, it's possible the machine isn't configured to receive that traffic on localhost
n
Nazeer Hussain
06/12/2020, 3:25 PMok got it, i am fixing 🙂
s
Soham
06/13/2020, 12:27 PMjust 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
i'm also seeing the same API status error
update: everything seemed to start working fine once i registered a flow!
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
n
Nazeer Hussain
06/15/2020, 11:52 AMNope @Soham, same issue persists, i tried everything, will keep you posted