We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessing librespeed through port 80 does not work (behind Caddy reverse proxy).
That the web ui is accessible.
In my docker-compose I had this:
ports: - "8264:80"
The container didn't work.
Container logs show this:
speedtest | + '[' 8080 '!=' 80 ']' speedtest | + is_alpine speedtest | + '[' -f /etc/alpine-release ']' speedtest | + sed -i 's/^Listen 80$/Listen 8080/g' /etc/apache2/ports.conf speedtest | + sed -i 's/*:80>/*:8080>/g' /etc/apache2/sites-available/000-default.conf
So I changed it to this:
ports: - "8264:8080"
And it worked.
- OS: - How docker service was installed:
x86-64
services: speedtest: container_name: speedtest image: ghcr.io/librespeed/speedtest:latest restart: unless-stopped environment: MODE: standalone #TITLE: "LibreSpeed" #TELEMETRY: "false" #ENABLE_ID_OBFUSCATION: "false" #REDACT_IP_ADDRESSES: "false" #PASSWORD: #EMAIL: #DISABLE_IPINFO: "false" #IPINFO_APIKEY: "your api key" #DISTANCE: "km" #WEBPORT: 80 ports: - "8264:8080" # webport mapping (host:container)
speedtest | + rm -rf '/var/www/html/*' speedtest | + cp /speedtest/speedtest.js /speedtest/speedtest_worker.js /var/www/html/ speedtest | + cp /speedtest/favicon.ico /var/www/html/ speedtest | + is_alpine speedtest | + '[' -f /etc/alpine-release ']' speedtest | + echo 'DEBIAN IMAGE' speedtest | DEBIAN IMAGE speedtest | + [[ standalone == \s\t\a\n\d\a\l\o\n\e ]] speedtest | + cp -r /speedtest/backend/ /var/www/html/backend speedtest | + '[' '!' -z '' ']' speedtest | + '[' standalone == backend ']' speedtest | + '[' standalone '!=' backend ']' speedtest | + cp /speedtest/ui.php /var/www/html/index.php speedtest | + [[ false == \t\r\u\e ]] speedtest | + is_alpine speedtest | + '[' -f /etc/alpine-release ']' speedtest | + chown -R www-data /var/www/html/backend /var/www/html/favicon.ico /var/www/html/index.php /var/www/html/speedtest.js /var/www/html/speedtest_worker.js speedtest | + '[' 8080 '!=' 80 ']' speedtest | + is_alpine speedtest | + '[' -f /etc/alpine-release ']' speedtest | + sed -i 's/^Listen 80$/Listen 8080/g' /etc/apache2/ports.conf speedtest | + sed -i 's/*:80>/*:8080>/g' /etc/apache2/sites-available/000-default.conf speedtest | + echo 'Done, Starting APACHE' speedtest | + is_alpine speedtest | + '[' -f /etc/alpine-release ']' speedtest | + exec apache2-foreground speedtest | Done, Starting APACHE speedtest | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.28.0.2. Set the 'ServerName' directive globally to suppress this message speedtest | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.28.0.2. Set the 'ServerName' directive globally to suppress this message speedtest | [Tue Dec 24 17:40:22.542611 2024] [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.62 (Debian) PHP/8.4.2 configured -- resuming normal operations speedtest | [Tue Dec 24 17:40:22.542648 2024] [core:notice] [pid 1:tid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Sorry, something went wrong.
Sorry I thought I was on the Linuxserver image.
No branches or pull requests
Is there an existing issue for this?
Current Behavior
Accessing librespeed through port 80 does not work (behind Caddy reverse proxy).
Expected Behavior
That the web ui is accessible.
Steps To Reproduce
In my docker-compose I had this:
The container didn't work.
Container logs show this:
So I changed it to this:
And it worked.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: