Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Reporting not responding #676

Open
MaxMoon771 opened this issue Jun 26, 2024 · 1 comment
Open

Error Reporting not responding #676

MaxMoon771 opened this issue Jun 26, 2024 · 1 comment
Assignees

Comments

@MaxMoon771
Copy link

I was enabling error reporting to determine my issues and concerns on iambic import issues I am facing. And the https connection to error-reporting-prod.iambic.org/report_exception is notwortking or timing out.

To Reproduce
Steps to reproduce the behavior:

  1. Enable Error Reporting in Config
    core:
    exception_reporting:
    enabled: true
    include_variables: false # Do not enable this feature unless you are certain that no sensitive information will be included in the report
    automatically_send_reports: true
    email_address: address

Error Message
2024/06/26 14:13:02 [error ] Unable to run exception reporting logic
error=HTTPSConnectionPool(host='error-reporting-prod.iambic.org', port=443): Max retries exceeded with url: /report_exception (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f1c62292c40>: Failed to establish a new connection: [Errno -2] Name or service not known'))

Community Engagement
Your vote counts! Please support this bug report by adding a 👍 reaction to the original issue, which will aid the community and maintainers in addressing this problem.

Please refrain from adding "+1" or "me too" comments, as these create unnecessary noise for issue followers and do not help in prioritizing the issue. If you wish to contribute to solving this issue or have submitted a pull request, please leave a comment.

@WillNye
Copy link
Collaborator

WillNye commented Nov 9, 2024

Thanks for the heads up. I'll try to get it back up and running within the next week.

@WillNye WillNye self-assigned this Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants