You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The speedtest-tracker application is encountering two primary issues:
Error Fetching External IP Address: The application fails to retrieve the external IP address, logging the following error:
[2025-01-19 18:39:16] production.ERROR: Failed to fetch external IP address. ["cURL error 28: Resolving timed out after 5002 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://icanhazip.com/"]
PostgreSQL Role Error: The PostgreSQL container logs repeatedly display the following fatal error:
FATAL: role "-d" does not exist
To Reproduce
Steps to reproduce the behavior:
Deploy the speedtest-tracker application using Docker as per the official documentation.
Start the Docker containers for both the application and the PostgreSQL database.
Monitor the application and database logs.
Observe the aforementioned errors in the respective logs.
Expected behavior
The application should successfully retrieve the external IP address without timing out, and the PostgreSQL database should operate without role-related errors.
Environment (please complete the following information):
[2025-01-19 18:39:16] production.ERROR: Failed to fetch external IP address. ["cURL error 28: Resolving timed out after 5002 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://icanhazip.com/"]
PostgreSQL Log:
2025-01-19 18:43:44.126 UTC [13428] FATAL: role "-d" does not exist
Additional context
The cURL error 28 suggests a timeout issue when attempting to resolve https://icanhazip.com/. This may indicate a DNS resolution problem or network connectivity issue within the container. Additionally, the PostgreSQL error indicates that there is an attempt to connect using a role named -d, which does not exist. This could be due to misconfigured environment variables or connection parameters in the application's database configuration.
I have verified network connectivity and DNS resolution within the container, and reviewed the database connection settings for accuracy. Despite these efforts, the issues persist. Any assistance or guidance to resolve these errors would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
[2025-01-19 18:39:16] production.ERROR: Failed to fetch external IP address. ["cURL error 28: Resolving timed out after 5002 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://icanhazip.com/"]
This one is thrown when the speedtest process can't reach the internet, if you're running Pihole or Adguard you'll need to allow-list that domain.
2025-01-19 18:43:44.126 UTC [13428] FATAL: role "-d" does not exist
As for this, I haven't see that before and likely an issue with the pgsql database. Make sure you didn't change the username or password of the database after the first start and that you've correctly set your puid and pgid.
Describe the bug
The speedtest-tracker application is encountering two primary issues:
[2025-01-19 18:39:16] production.ERROR: Failed to fetch external IP address. ["cURL error 28: Resolving timed out after 5002 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://icanhazip.com/"]
PostgreSQL Role Error: The PostgreSQL container logs repeatedly display the following fatal error:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The application should successfully retrieve the external IP address without timing out, and the PostgreSQL database should operate without role-related errors.
Environment (please complete the following information):
Screenshots
N/A
Logs
Application Log:
[2025-01-19 18:39:16] production.ERROR: Failed to fetch external IP address. ["cURL error 28: Resolving timed out after 5002 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://icanhazip.com/"]
PostgreSQL Log:
2025-01-19 18:43:44.126 UTC [13428] FATAL: role "-d" does not exist
Additional context
The cURL error 28 suggests a timeout issue when attempting to resolve https://icanhazip.com/. This may indicate a DNS resolution problem or network connectivity issue within the container. Additionally, the PostgreSQL error indicates that there is an attempt to connect using a role named -d, which does not exist. This could be due to misconfigured environment variables or connection parameters in the application's database configuration.
I have verified network connectivity and DNS resolution within the container, and reviewed the database connection settings for accuracy. Despite these efforts, the issues persist. Any assistance or guidance to resolve these errors would be greatly appreciated.
The text was updated successfully, but these errors were encountered: