@Marvin i updated my prefect server from 2.14.11 to 2.14.14 now the ui is only showing blank screen. while inspecting it is showing err_name_not_resolved. how do i fix this

From what I've gathered, the error

ERR_NAME_NOT_RESOLVED

typically indicates a DNS resolution problem, meaning the browser is unable to find the server's IP address. This isn’t directly mentioned in Prefect’s documentation or GitHub issues, but here are some steps you can take to troubleshoot and potentially resolve the issue: 1. Check Your Prefect Server URL: Ensure that the URL you are using to access the Prefect UI is correct. The default is usually

<http://127.0.0.1:4200>

if you're running it locally. 2. Clear DNS Cache: - On Windows, use the command:

ipconfig /flushdns

- On macOS, use the command:

sudo killall -HUP mDNSResponder

- On Linux, depending on your system, you might use:

sudo systemd-resolve --flush-caches

3. Browser Cache and Cookies: - Try a hard refresh:

Cmd+Shift+R

(Mac) or

Ctrl+Shift+R

(Windows/Linux). - Clear your browser history, cookies, and cache and then try accessing the UI again. 4. Check Network Configuration: - Ensure that your device’s network settings are properly configured. - Make sure your DNS settings are not misconfigured. 5. Restart Prefect Server: - Use the command

prefect server start

to restart your server.

bash
    prefect server start

6. Check Host File: - Ensure your OS host file doesn’t contain incorrect mappings that prevent DNS resolution. If none of these steps work, you might need to look into any specific network policies or firewall rules that could be blocking access or consult the Prefect community support. For more detailed reference, you can visit: - Hosting a Prefect server instance - Connecting to Prefect Cloud If the problem persists, consider reaching out on Prefect's support channels or their GitHub issues page.

@Ying Ting Loo were you able to resolve this? I am having the same issue

just update the version. I think theres an issue with the version2.14.14. updated to 2.14.21 fixed it

That's what I ended up doing 🙂 I used 2.15. Thanks!!