You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up the UI using a Cloudflare tunnel, the setup does not complete. It gives the error "Error
The hostname <bunkerweb.example.net> is already in use.", even if the hostname correctly points to the UI container. The expected behavior is that the setup continues.
How to reproduce?
Have a host with cloudflared installed, and set up a tunnel, "bunkerweb.example.com" (names are examples), resolving to localhost:80. Set up bunkerweb in the yaml file you provide docker-compose so that bunkerweb.example.com goes to the UI container "bw-ui". Launch your container group, and connect to bunkerweb.example.com. Fill out the UI for first time signin, setting REVERSE_PROXY_HOST to what is specified in the docker-config.yml file, REVERSE_PROXY_URL to any value, and server name to bunkerweb.example.com.
What happened?
When setting up the UI using a Cloudflare tunnel, the setup does not complete. It gives the error "Error
The hostname <bunkerweb.example.net> is already in use.", even if the hostname correctly points to the UI container. The expected behavior is that the setup continues.
How to reproduce?
Have a host with cloudflared installed, and set up a tunnel, "bunkerweb.example.com" (names are examples), resolving to localhost:80. Set up bunkerweb in the yaml file you provide docker-compose so that bunkerweb.example.com goes to the UI container "bw-ui". Launch your container group, and connect to bunkerweb.example.com. Fill out the UI for first time signin, setting REVERSE_PROXY_HOST to what is specified in the docker-config.yml file, REVERSE_PROXY_URL to any value, and server name to bunkerweb.example.com.
Configuration file(s) (yaml or .env)
Relevant log output
BunkerWeb version
1.5.10
What integration are you using?
Docker
Linux distribution (if applicable)
Ubuntu 24.04.1 LTS x86_64
Removed private data
Code of Conduct
The text was updated successfully, but these errors were encountered: