Troubleshooting Phoenix Server Connection Error with Experiments

Daniel N. · 2025-04-14T13:57:24.827Z

Hi guys, I'm currently following your guide on running experiments. Everything works perfectly when I run them locally using the dry_run parameter. However, when I try to send the experiments to our hosted Phoenix server, I encounter the following error: ConnectError: [WinError 10061] No connection could be made because the target machine actively refused it Our Phoenix server has authentication enabled, so I’m wondering if that could be the cause. When instrumenting the application, I’m including the Phoenix API key in the request headers as instructed. Is there anything else I need to configure to get this working with an authenticated Phoenix instance? Any suggestions or guidance would be greatly appreciated!

Troubleshooting Phoenix Server Connection Error with Experiments | Arize AI Community

5 comments

· Sorted by Oldest

Daniel N.
·
RunLLM
RunLLM
APP
·
To resolve the connection error when sending experiments to a hosted Phoenix server with authentication enabled, ensure that you have correctly set the `PHOENIX_API_KEY` environment variable. This key should be included in the request headers to authenticate with the server. Additionally, verify that the `PHOENIX_COLLECTOR_ENDPOINT` is correctly configured to point to your Phoenix server's endpoint. According to the <https://docs.arize.com/phoenix/self-hosting/configuration#client-configuration|Phoenix documentation>, you should set the `PHOENIX_API_KEY` and `PHOENIX_COLLECTOR_ENDPOINT` environment variables in your application. If authentication is enabled, all interactions with the server need to include an authorization header, which Phoenix will automatically include if the `PHOENIX_API_KEY` is set. If you continue to experience issues, ensure that the server is accessible from your network and that there are no firewall rules blocking the connection. Would you like more detail on setting up these configurations? Sources: - <https://docs.arize.com/phoenix/self-hosting/configuration#client-configuration|Phoenix documentation>
💡 Hint: Mention RunLLM in the thread for followups.
RunLLM
APP
·
The error you're encountering, `ConnectError: <https://docs.arize.com/phoenix/deployment/authentication#B%3A4|WinError 10061] No connection could be made because the target machine actively refused it`, typically indicates that the server is not reachable at the specified endpoint. Since your Phoenix server has authentication enabled, ensure that the `PHOENIX_API_KEY` environment variable is correctly set and included in your request headers. According to [Phoenix documentation>, you should set the `PHOENIX_API_KEY` environment variable to include the API key in the authorization header automatically. Additionally, verify that the endpoint URL is correct and accessible from your network. If the server is behind a firewall or requires specific network configurations, ensure those are correctly set up. If the issue persists, check the server logs for any authentication-related errors or network issues. Would you like more detailed steps on setting up the environment variables or troubleshooting network issues? Sources: - <https://docs.arize.com/phoenix/deployment/authentication#B%3A4|Phoenix documentation>
💡 Hint: Mention RunLLM in the thread for followups.
Daniel N.
·
We are hosting phoenix on Azure. The tracing and span annotations are working great!
Daniel N.
·
Oh that was the issue, I was typing the URL directly instead of using the PHOENIX_COLLECTOR_ENDPOINT 😅 Thank you!
🙌1

Daniel N.
·
RunLLM
RunLLM
APP
·
To resolve the connection error when sending experiments to a hosted Phoenix server with authentication enabled, ensure that you have correctly set the `PHOENIX_API_KEY` environment variable. This key should be included in the request headers to authenticate with the server. Additionally, verify that the `PHOENIX_COLLECTOR_ENDPOINT` is correctly configured to point to your Phoenix server's endpoint. According to the <https://docs.arize.com/phoenix/self-hosting/configuration#client-configuration|Phoenix documentation>, you should set the `PHOENIX_API_KEY` and `PHOENIX_COLLECTOR_ENDPOINT` environment variables in your application. If authentication is enabled, all interactions with the server need to include an authorization header, which Phoenix will automatically include if the `PHOENIX_API_KEY` is set. If you continue to experience issues, ensure that the server is accessible from your network and that there are no firewall rules blocking the connection. Would you like more detail on setting up these configurations? Sources: - <https://docs.arize.com/phoenix/self-hosting/configuration#client-configuration|Phoenix documentation>
💡 Hint: Mention RunLLM in the thread for followups.
RunLLM
APP
·
The error you're encountering, `ConnectError: <https://docs.arize.com/phoenix/deployment/authentication#B%3A4|WinError 10061] No connection could be made because the target machine actively refused it`, typically indicates that the server is not reachable at the specified endpoint. Since your Phoenix server has authentication enabled, ensure that the `PHOENIX_API_KEY` environment variable is correctly set and included in your request headers. According to [Phoenix documentation>, you should set the `PHOENIX_API_KEY` environment variable to include the API key in the authorization header automatically. Additionally, verify that the endpoint URL is correct and accessible from your network. If the server is behind a firewall or requires specific network configurations, ensure those are correctly set up. If the issue persists, check the server logs for any authentication-related errors or network issues. Would you like more detailed steps on setting up the environment variables or troubleshooting network issues? Sources: - <https://docs.arize.com/phoenix/deployment/authentication#B%3A4|Phoenix documentation>
💡 Hint: Mention RunLLM in the thread for followups.
Daniel N.
·
We are hosting phoenix on Azure. The tracing and span annotations are working great!
Daniel N.
·
Oh that was the issue, I was typing the URL directly instead of using the PHOENIX_COLLECTOR_ENDPOINT 😅 Thank you!
🙌1