Hi team! First message here :muscle: I am having s...
# show-and-tell
j
Hi team! First message here 💪 I am having some issues with the prefect local server UI. I am registering flows in order to run them from the UI, but the given url sends me to a blank page, with no trace of the flow.
This is the output in jupyter notebooks:
but the ui stays blank:
however, flow runs properly when using flow.run(). Thanks in advance for your time!
k
Hey Josep, Are there any exceptions raised when you are building the UI after running
prefect backend server
and
prefect server start
?
j
Hey Kyle! Don't know for sure, but I believe everything went as expected (no strange behaviour nor any exception raised). This is something that has worked for me since I first installed prefect, so it is kind of weird. I may reboot my pc as I have other instances of anaconda that could be messing with my prefect environment. I'll let you know tomorrow morning if everything is working back again, just wanted to know if this was something general or just bad luck on my side 🙂
k
Please do! That is weird, we should definitely be able to get you sorted.
👍 1
j
Good morning! Seems like I'm still facing the issue. The register process is working and I can run any flow locally, but it seems as if the ui wasn't linked to my computer. I've checked for previous flows I had registered, and nothing appears (completely blank). I may be wrong, but I feel as if the agent wasn't starting properly, or at least wasn't linking properly to my prefect environment (anaconda).
👀 1
n
Hi @Josep Consuegra Navarrina! Are you running the Prefect Server setup in a remote environment like an EC2 or GCP machine?
j
Hi Nicholas! Currently running everything in local, so no EC2 or GCP machine. I'm restarting again, as maybe I'm messing up some config in anaconda
n
@Josep Consuegra Navarrina any luck? It sounds like the UI might not be able to talk to the API for some reason
j
Hi Nicholas! Since I'm not seeing anything in the UI (at all) and I had previous versions of flows deployed there, it feels like I'm registering flows elsewhere (as I don't get any error message) but it is showing me something else. I guess there is a repository where all my existing and newly deployed flows are stored, but it may be inaccessible to me (I see the UI, only the names of the flows I register do not exist there). Thanks for your time!!
d
FWIW I experienced what sounds like the same problem, with flow.register seeming to report a successful registration, providing a URL to local prefect server UI install, but no Flows listed and blank page when I clicked the link. Following for now, will try to make another attempt at this ASAP
n
@Dan DiPasquo - feel free to start a new thread in #CL09KU1K7 if you run into issues!
j
Hi Nicholas! Still with the same issues, but I've seen in the slack channels that other people are facing the same issue when doing a prefect start server even though a prefect server is running already. Could this be the issue? I saw someone posting an answer to solve this issue, yet I didn't quite understand the actions to do. Additionaly, I don't know if there's any logfile where I can debug the prefect server in order to see what is failing on my end. Thanks for your time!
n
Hi @Josep Consuegra Navarrina sorry for the slow response, bit chaotic over here this morning. That could be an issue, particularly if ports are already allocated. One way to test that would be the solutions posted here. Since all of the Prefect Server infrastructure runs in Docker, you'll be able to see if another instance is already running with
docker ps
.
j
Hi Nicholas! I've tried what you mentioned in your post, yet nothing is working on my side. I don't know if it can be helpful, but please find attached the "prefect server start" output I see in my console. I see a few connectivity errors during the setup, but it appears to me as if everything is properly working in the end. Additionally, whenever a flow is registered, several POST lines appear in the console, which I understand as it working as intended (except nothing appears in the UI). Thanks again for your time!
is it possible that my corporate vpn is messing up the connectivity with the docker containers?
n
@Josep Consuegra Navarrina it's looking to me like the
graphql_url
variable in you ~/.prefect/config.toml` is defined but defined with perhaps an empty string? This is the output I'd expect if it were set correctly:
Yours looks like this:
ui_1         | Replacing graphql references with:
j
Hi Nicholas! Surprisingly, I don't seem to have a config.toml file, yet I can see that all the flows I'm registering are being updated in the corresponding folder.
Do you know any way to fix that? seems like my ui and the graphql server are not communicating properly
n
Hi @Josep Consuegra Navarrina - let's try by adding the
~/.prefect/config.toml
file and including this in it:
Copy code
[server]
  [server.ui]
  graphql_url = "<http://localhost:4200/graphql>"
After that's added, you'll want to restart prefect server and re-register your flows
j
Hi nicholas! sorry it took so long, but I've been out of the office a few days. I've tried what you mentioned, yet the following error appears now:
I've restarted prefect server and re-registered the flow, yet the api doesn't seem to connect again
n
Hi @Josep Consuegra Navarrina - the API Status tile reports it's trying to connect to an api at
/
, which wouldn't exist. Have you set your
graphql_url
variable in
~/.prefect/config.toml
to your endpoint as I described above?
j
Hi nicholas, I created a config.toml file in the .prefect folder with the content you mentioned, although as you mentioned it doesn't seem to be working
n
Hm ok, can you give me the details of your setup? Where have you installed Prefect Server, where is the
config.toml
(and what's in it), etc
j
Hi nicholas! been on holidays for a few days, sorry for the delay. I have installed Prefect server in C:\Users\josepconsuegra\.prefect, where the config.toml file is located. However, this file had nothing in it, as far as I remember. I've added the snippet you mentioned in this thread, so now its content is: [server] [server.ui] graphql_url = "http://localhost:4200/graphql"
n
Hi @Josep Consuegra Navarrina - any luck when restarting the server after that?
j
Not really, apparently now it doesn't link to the UI (same case as in the last picture)