Error starting airbyte-webapp container on EC2

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The airbyte-webapp container fails to start on EC2 with the error message ‘nginx: [emerg] socket() [::]:8080 failed (97: Address family not supported by protocol)’. The user followed the guide for deploying Airbyte on AWS EC2 and has not made any configuration changes.


Question

Hi I am trying to install latest Airbyte on EC2 amazon-linux and the airbyte-webapp container fails to start.
When I look in the logs I see:
nginx: [emerg] socket() [::]:8080 failed (97: Address family not supported by protocol)
I have not changed any configuration and roughly followed this guide:
https://docs.airbyte.com/deploying-airbyte/on-aws-ec2

This is how I see my containers:

6e37a470b720   airbyte/proxy:0.63.2                      "./run.sh ./run.sh"      29 minutes ago   Up 23 minutes                   0.0.0.0:8000-8001->8000-8001/tcp, 0.0.0.0:8003->8003/tcp, 80/tcp, 0.0.0.0:8006->8006/tcp   airbyte-proxy
6a1cc17e4b74   airbyte/webapp:0.63.2                     "/docker-entrypoint.…"   29 minutes ago   Restarting (1) 15 seconds ago                                                                                              airbyte-webapp
0388ed023474   airbyte/cron:0.63.2                       "/bin/bash -c airbyt…"   29 minutes ago   Up 23 minutes                                                                                                              airbyte-cron
5d1c0ac5f333   airbyte/connector-builder-server:0.63.2   "/bin/bash -c airbyt…"   29 minutes ago   Up 23 minutes                   0.0.0.0:32774->8080/tcp                                                                    airbyte-connector-builder-server
497dd7d545c1   airbyte/airbyte-api-server:0.63.2         "/bin/bash -c airbyt…"   29 minutes ago   Up 23 minutes                   5005/tcp, 0.0.0.0:32776->8006/tcp                                                          airbyte-api-server
a72e59b8dada   airbyte/server:0.63.2                     "/bin/bash -c airbyt…"   29 minutes ago   Up 23 minutes                   5005/tcp, 8000/tcp, 0.0.0.0:32777->8001/tcp                                                airbyte-server
2e77e0148596   airbyte/worker:0.63.2                     "/bin/bash -c airbyt…"   29 minutes ago   Up 23 minutes                   5005/tcp, 0.0.0.0:32775->9000/tcp                                                          airbyte-worker
ba921bcdbc38   airbyte/db:0.63.2                         "docker-entrypoint.s…"   29 minutes ago   Up 24 minutes                   5432/tcp                                                                                   airbyte-db
de32e9327f53   airbyte/temporal:0.63.2                   "./update-and-start-…"   29 minutes ago   Up 24 minutes                   6933-6935/tcp, 6939/tcp, 7233-7235/tcp, 7239/tcp                                           airbyte-temporal
cef5874b148a   alpine/socat                              "socat -t 900 TCP-LI…"   29 minutes ago   Up 24 minutes                   0.0.0.0:32773->2375/tcp                                                                    airbyte-docker-proxy-1```

Does anyone knows what might cause this issue?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1719311665946189) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["error", "airbyte-webapp", "container", "ec2", "nginx", "address-family", "protocol"]
</sub>