Hi, quick question: I deployed prefect server in a...
# prefect-community
n
Hi, quick question: I deployed prefect server in a VM in azure and everything works fine except I cannot change the default
apollo_url
like described here: https://docs.prefect.io/orchestration/server/deploy-local.html#ui-configuration I do this in `~/.prefect/config.toml`:
Copy code
[server]
  [server.ui]
  apollo_url="http://<server_url>:4200/graphql"
then:
prefect server start
and it still uses the default
localhost
hence I have to manually change it in the server UI. Any idea why?
n
Hi @Nuno Silva - which version of Prefect are you on?
n
0.13.8 (forgot to mention sorry)
n
no worries!
Can you visit your UI endpoint but with
/settings.json
at the end of it? So if it's localhost it would be
<http://localhost:8080/settings.json>
n
yes, it outputs:
Copy code
{
  "server_url": "http://<correct_server_url>:4200/graphql"
}
n
perfect! ok so then most likely this is a caching issue; if you go to the
Home
page and click the restore button, it'll clear your local storage
n
I don't have that option yet, even though I running 0.13.8
but looking into the prefect UI you have this:
last deployed 2 weeks ago, that is weird
n
oh interesting ok that's my bad i thought that went out with the last core release. in which case you have 3 options: 1. pull the
latest
or
master
tags for the UI (they should actually be the same) 2. wait till the next core release, which should be later today 3. try manually clearing your local storage by opening the chrome console and typing
localStorage.clear()
n
ok thanks, I'll try option 2 and 3 and ask again if needed. thank you
n
Yeah no problem, let me know if you run into anything else, this is still a workflow we're tweaking a bit
n
@nicholas latest release 0.13.8 solves the problem, that reset local storage option you mentioned works. FYI: when I did it in chrome and deleted the prefect ui cookies after changing the setting, it was defaulting to localhost again. So I cleared the cookies, opened an incognito window and did the reset local storage there and seems ok.
n
Interesting @Nuno Silva - thanks for the info. I'm thinking perhaps we only want to persist the decision in localstorage if it's a Cloud instance (rather than Server). I'll see if there's a better UX here
n
ok, sounds good, thanks.