On the Airflow web UI as admin user on Admin tab connections getting error #35183
-
Hello, #######################################
Ooops!
Something bad has happened.
Airflow is used by many users, and it is very likely that others had similar problems and you can easily find
a solution to your problem.
Consider following these steps:
* gather the relevant information (detailed logs with errors, reproduction steps, details of your deployment)
* find similar issues using:
* GitHub Discussions
* GitHub Issues
* Stack Overflow
* the usual search engine you use on a daily basis
* if you run Airflow on a Managed Service, consider opening an issue using the service support channels
* if you tried and have difficulty with diagnosing and fixing the problem yourself, consider creating a bug report.
Make sure however, to include all relevant details and results of your investigation so far.
Python version: 3.7.17
Airflow version: 2.6.2
Node: redact
-------------------------------------------------------------------------------
Error! Please contact server admin.
######################################### |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 8 replies
-
Without webserver logs it is hard to say what is going wrong. But let's me guess that it is related to: |
Beta Was this translation helpful? Give feedback.
-
Dear Team, We tried to uninstall airflow, deleted the secrets referencing the airlfow and tried to re-install the same. However, we are encourntering the same error. I believe during the installation fernet key should get generated/encrypted by itself. Could you please investigate further and suggest us next steps. We are seeing the same log trace as posted earlier. Thanks |
Beta Was this translation helpful? Give feedback.
-
hi jens |
Beta Was this translation helpful? Give feedback.
-
Hi Jens, Thanks |
Beta Was this translation helpful? Give feedback.
-
Hi @Taragolis @jens-scheffler-bosch @potiuk Thanks for the Support Now my issue got fixed 👍 Cheers, |
Beta Was this translation helpful? Give feedback.
Then something in your setup is severely broken. If the stack trace is really the same, then something is generally broken but nothing that can be diagnosed from far away.
Maybe you need to drop the full db instance and start over from scratch.