5XX errors after enabling ingress for webapp but not server services

Slack Knowledge Base Q&A API, Terraform and Other Topics
, , , ,
1

Summary

Enabling ingress for the webapp but not the server services causing 5XX errors, including HTTP/1.1 500 Internal Server Error when running terraform apply. Question about the relationship between enabling ingress for different services within the Airbyte context.


Question

Hi everyone, I’m having multiple 5XX errors since enabling ingress for the webapp but not the server services (including HTTP/1.1 500 Internal Server Error when I try to run terraform apply). When I check <#C01AHCD885S|ask-ai>, it always replies that it’s not recommended to enable ingress for one service but not the other. However, the devops team in my company says this shouldn’t be the case. Can these two things be related within the Airbyte context?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["5xx-errors", "enabling-ingress", "webapp", "server-services", "http-500-error", "terraform", "airbyte-context"]
2

I’d be more concerned about errors than ingress itself. In my current setup, I have only ingress for webapp and it’s working just fine.
Have you checked logs of your containers/pods while running terraform apply?

3

thank you so much! :slightly_smiling_face: I did, and found this error:

java.lang.IllegalArgumentException: No enum constant <http://io.airbyte.api.client.model.generated.Geography.eu|io.airbyte.api.client.model.generated.Geography.eu>```
but I couldn't see how it was related or how to resolve it..

I think I've found the issue now though and will share in case other people have similar experiences.

For the `terraform apply` issue specifically, it seems somewhat similar to <https://github.com/airbytehq/terraform-provider-airbyte/issues/24|this issue> that was previously resolved. Disabling the API server service (as suggested <https://github.com/airbytehq/terraform-provider-airbyte/issues/89#issuecomment-2202665884|here>) and connecting the terraform provider directly to the server service resolved the issue.

We didn't experience other server issues consistently enough for me to say yet if they're fixed.