I’m running orion `2.0b2` and starting the server ...
# prefect-community
r
I’m running orion
2.0b2
and starting the server (on an EC2 machine) with an IP on a different port. (self-hosted). I’m able to connect to it via browser (I’ve set all the security groups and routes to allow me to connect to it on a browser). However it seems that internally Prefect Orion is still interacting with the default host and port. So the UI doesn’t render all the info (see screenshot in the thread) Is there something extra I need to change?
k
Hey @Ricardo Gaspar, could you move some of the traceback to the thread to not crowd the main channel too much? I think what you are running into is the the Orion UI uses a hardcoded API URL to 127.0.0.1:4200. This will be changed in the next release to respect the config. In the mean time though, Cloud 2.0 is a good way to interact with Orion remotely. Have you tried it? The Cloud 2.0 UI is different
upvote 1
👍 1
r
traceback info starting server prefect orion :
Copy code
efect-server.service - Prefect Server
     Loaded: loaded (/etc/systemd/system/prefect-server.service; disabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-04-07 15:15:26 UTC; 4min 22s ago
   Main PID: 13902 (prefect)
      Tasks: 5 (limit: 18834)
     Memory: 179.3M
     CGroup: /system.slice/prefect-server.service
             ├─13902 /usr/bin/python3 /usr/local/bin/prefect orion start --ui --host 10.1.211.196 --port 8080
             └─13904 /usr/bin/python3 /usr/local/bin/uvicorn --factory prefect.orion.api.server:create_app --host 10.1.211.19>

Apr 07 15:15:26 ip-10-1-211-196 systemd[1]: Started Prefect Server.
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]: Starting...
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]:  ___ ___ ___ ___ ___ ___ _____    ___  ___ ___ ___  _  _
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]: | _ \ _ \ __| __| __/ __|_   _|  / _ \| _ \_ _/ _ \| \| |
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]: |  _/   / _|| _|| _| (__  | |   | (_) |   /| | (_) | .` |
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]: |_| |_|_\___|_| |___\___| |_|    \___/|_|_\___\___/|_|\_|
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]: Configure Prefect to communicate with the server with:
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]:     prefect config set PREFECT_API_URL=<http://10.1.211.196:8080/api>
Apr 07 15:15:27 ip-10-1-211-196 prefect[13902]: Check out the dashboard at <http://10.1.211.196:8080>
I’ve even set these values as environment variables and they show config on my profile:
Copy code
root@ip-10-1-211-196:~# prefect config view --show-sources
PREFECT_PROFILE='default'
PREFECT_ORION_API_HOST='10.1.211.196' (from env)
PREFECT_ORION_API_PORT='8080' (from env)
So the UI doesn’t render all the info (see screenshot in the thread)
m
I've experienced something similar and thought I'd just misconfigured something! Good to hear this won't be hard-coded in the next release
👍 1
k
Cloud is usable though because it has a different UI
m
What's the difference between orion and cloud 2.0? From looking at this blog post they look the same? Is it just self-hosted / managed?
k
Cloud is hosted and has concepts like workspaces so you can interact with multiple Orion instances (think dev/staging/prod)
a
Just for reference, in this issue, Michael mentioned we are already working on a fix to this hardcoded API URL issue https://github.com/PrefectHQ/prefect/issues/5648
👌 1