I want to change the webserver port from 8000 to something else. How can I do that?

To change the webserver port from 8000 to something else, you can modify the

API_URL

in your

.env

file and restart Airbyte. If you are using

abctl

to install Airbyte, you can specify a different port by passing the

--port

flag to the

local install

command. For example,

abctl local install --port 6598

. Here are the steps: 1. Open your

.env

file and find the

API_URL

line. 2. Change the port number in the

API_URL

to your desired port. 3. Save the

.env

file. 4. Restart Airbyte. If you are using `abctl`: 1. Run the

abctl local install --port <your-desired-port>

command. Please ensure that the security group configured for your instance allows traffic in on the port that you deploy Airbyte on. Sources: - [Connect to Airbyte on AWS EC2](https://docs.airbyte.com/deploying-airbyte/on-aws-ec2#connect-to-airbyte) - [Using an EC2 Instance with abctl](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#using-an-ec2-instance-with-abctl)

I have webapp_url and not api_url in .env file.

The

WEBAPP_URL

environment variable is used to define the URL where the Airbyte Webapp is hosted. This includes the port and is used by Airbyte services. If you want to change the Airbyte instance URL provided in notifications, you can set this variable to your custom domain name. On the other hand,

API_URL

is another environment variable that is used in the configuration of Airbyte. It is not present as an environment variable but is required for webapp configuration. If you only have

WEBAPP_URL

in your

.env

file and not

API_URL

, you might need to add

API_URL

depending on your specific use case or configuration. Here is an example of how these variables can be declared in the

.env

file:

bash WEBAPP_URL=<http://localhost:8000/> API_URL=/api/v1/

Please refer to the Airbyte documentation or the specific instructions related to your setup for more details. Sources: - [Github Issue (open): [docker] AWS Secret Manager Broken after Upgrading to

v0.50.35

> Comments Part 4](https://github.com/airbytehq/airbyte/issues/33121) - [Documentation > Operator-guides > Configuring Airbyte > Reference > Shared > Airbyte Services](https://docs.airbyte.com/operator-guides/configuring-airbyte#airbyte-services)

@kapa.ai I have added api_url also as /api/v1 and webapp_url as http://localhost:9001. And after restart also its not starting at 9001 port.

A message from kapa.ai

The

WEBAPP_URL

and

API_URL

environment variables are used to define the URLs where the Airbyte Webapp and API are hosted, respectively. However, changing these values in the

.env

file does not change the ports on which these services are running. These variables are used for routing and configuration purposes within the application, not for changing the actual ports the services listen on. If you want to change the port on which the Airbyte web server is running, you would typically need to modify the Docker Compose setup or the specific service configuration, not the

.env

file. For example, in a Docker Compose setup, you would need to change the port mapping for the

airbyte-webapp

service in the

docker-compose.yaml

file. However, based on the provided knowledge sources, there isn't a specific guide or instruction on how to change the web server's port in Airbyte. It's recommended to check the official Airbyte documentation or reach out to the Airbyte community for further assistance. Sources: - [Forum Post: Change webserver port in docker compose setup](https://discuss.airbyte.io/t/3876) - [Documentation > Deploying-airbyte > Deploy Airbyte on AWS (Amazon EC2) > Connect to Airbyte](https://docs.airbyte.com/deploying-airbyte/on-aws-ec2#connect-to-airbyte)

@kapa.ai I want to run airbyte on 9001 server. What all files I need to change?

A message from kapa.ai

To change the port on which Airbyte runs, you would need to modify the Docker Compose setup. Specifically, you would need to change the port mapping for the

airbyte-server

and

airbyte-webapp

services in the

docker-compose.yaml

file. Here's an example of what you might need to change:

yaml services:   airbyte-server:     ports:       - 9001:8001   airbyte-webapp:     ports:       - 9001:80

In this example, the

airbyte-server

service, which by default listens on port 8001, is mapped to port 9001 on your host machine. Similarly, the

airbyte-webapp

service, which by default listens on port 80, is also mapped to port 9001 on your host machine. Please note that mapping two services to the same host port as shown in the example above will likely cause a port conflict. You would typically assign a unique host port to each service. After making these changes, you would need to restart your Airbyte deployment for the changes to take effect. Please note that the exact changes may vary depending on your specific setup and configuration. Always refer to the official Airbyte documentation and your specific deployment configuration for the most accurate information. Sources: - [Forum Post: Change webserver port in docker compose setup](https://discuss.airbyte.io/t/3876) - [Documentation > Deploying-airbyte > Deploy Airbyte on AWS (Amazon EC2) > Connect to Airbyte](https://docs.airbyte.com/deploying-airbyte/on-aws-ec2#connect-to-airbyte)

@kapa.ai I have changed ports inside airbyte-proxy of docker-compose file. And changed .env file. Other than that I am not able to find any config where I will need to make a change.

A message from kapa.ai

If you have already updated the port mappings in the

docker-compose.yaml

file and updated the

.env

file, you have covered the main areas where port configurations are specified for Airbyte. Here's a quick recap of the changes you need to make: 1. Update the

docker-compose.yaml

file: Change the port mapping for the

airbyte-server

and

airbyte-webapp

services to the desired port.

yaml services:   airbyte-server:     ports:       - 9001:8001   airbyte-webapp:     ports:       - 9001:80

2. Update the

.env

file: Change the

API_URL

and

WEBAPP_URL

environment variables to reflect the new port.

bash API_URL=<http://localhost:9001/api/v1/> WEBAPP_URL=<http://localhost:9001/>

After making these changes, you should restart your Airbyte deployment for the changes to take effect. If you've done all of this and are still facing issues, it's possible that there might be other factors at play, such as firewall rules, network settings, or other services running on the same port. You might want to check these aspects as well. Sources: - [Forum Post: Change webserver port in docker compose setup](https://discuss.airbyte.io/t/3876) - [Documentation > Deploying-airbyte > Deploy Airbyte on AWS (Amazon EC2) > Connect to Airbyte](https://docs.airbyte.com/deploying-airbyte/on-aws-ec2#connect-to-airbyte)

@kapa.ai I want to run 3 instances of airbyte on the same linux server, how can I do it.

A message from kapa.ai

Running multiple instances of Airbyte on the same server can be challenging due to potential conflicts with ports, container names, and other resources. However, it's possible to deploy multiple instances of Airbyte on the same or multiple clusters using Restack as mentioned in the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-restack#deploy-multiple-instances-of-airbyte). Here are the general steps you would need to follow: 1. Clone the Airbyte repository for each instance: You would need to clone the Airbyte repository into separate directories for each instance you want to run.

bash # clone Airbyte from GitHub into a new directory for instance 1 git clone --depth=1 <https://github.com/airbytehq/airbyte.git> airbyte1  # clone Airbyte from GitHub into a new directory for instance 2 git clone --depth=1 <https://github.com/airbytehq/airbyte.git> airbyte2  # clone Airbyte from GitHub into a new directory for instance 3 git clone --depth=1 <https://github.com/airbytehq/airbyte.git> airbyte3

2. Modify the Docker Compose files: For each instance, you would need to modify the

docker-compose.yaml

file to use different ports for each service to avoid conflicts. For example, you could run the first instance on the default ports, the second instance on ports 9001-9003, and the third instance on ports 9004-9006. 3. Start each instance: Navigate to each directory and start each instance using the

./run-ab-platform.sh

script.

bash # start instance 1 cd airbyte1 ./run-ab-platform.sh  # start instance 2 cd ../airbyte2 ./run-ab-platform.sh  # start instance 3 cd ../airbyte3 ./run-ab-platform.sh

Please note that this is a general guide and the exact steps may vary depending on your specific setup and configuration. Always refer to the official Airbyte documentation and your specific deployment configuration for the most accurate information. Also, it's worth noting that a user on the Airbyte GitHub discussions reported issues when trying to run two separate Airbyte Docker instances on one server. The user reported that changing container names caused some internal code of the application to stop working and two containers kept restarting. As of the time of the discussion, there was no official answer or solution provided by the Airbyte team. You can follow the discussion [here](https://github.com/airbytehq/airbyte/discussions/32809) for updates.