Apache2 reverse proxy does not work ARM64 #1484

New Issue

OVERLORD · 2026-02-05T01:03:52+03:00

OVERLORD commented

2026-02-05 01:03:52 +03:00

Originally created by @Toni-d-e-v on GitHub (Jan 28, 2023).

Docker

70d69ab367cf   vaultwarden/server   "/usr/bin/entry.sh /…"   44 minutes ago   Up 30 minutes (healthy)   80/tcp, 0.0.0.0:3012->3012/tcp, :::3012->3012/tcp, 0.0.0.0:8088->8080/tcp, :::8088->8080/tcp   vaultwarden

Apache2 conf


<VirtualHost *:80>
    ServerName my.domain.com

    #SSLCertificateFile ${SSLCERTIFICATE}
    #SSLCertificateKeyFile ${SSLKEY}
    #SSLCACertificateFile ${SSLCA}
    #${SSLCHAIN}

    ErrorLog /home/ubuntu/dockers/vaultwarden/bitwarden-error.log
    CustomLog /home/ubuntu/dockers/vaultwarden/bitwarden-access.log combined

#    RewriteEngine On
#    RewriteCond %{HTTP:Upgrade} =websocket [NC]
#    RewriteRule /notifications/hub(.*) ws://0.0.0.0:3012/$1 [P,L]
    RewriteEngine On
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteCond %{HTTP:Connection} upgrade [NC]
    RewriteRule ^/?(.*) "ws://127.0.0.1:3012/$1" [P,L]
    ProxyPass / http://127.0.0.1:8080/



    ProxyPreserveHost On
    ProxyRequests Off
    RequestHeader set X-Real-IP %{REMOTE_ADDR}s
    # Add this line if your url attributes are reported back as http://... :
    RequestHeader add X-Forwarded-Proto https
RewriteCond %{SERVER_NAME} =my.domain.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

Issue

HTTPS Is enabled and here are the logs

Custom logs!

[Sat Jan 28 11:01:49.607972 2023] [proxy:error] [pid 35283] (111)Connection refused: AH00957: http: attempt to connect to 0.0.0.0:8080 (0.0.0.0) failed
[Sat Jan 28 11:01:49.608007 2023] [proxy_http:error] [pid 35283] [client 93.231.123.17:39088] AH01114: HTTP: failed to make connection to backend: 0.0.0.0,

Server

I'm using amr64 server that runs docker, its cloud instance of oracle and I got no issues running nextcloud

Originally created by @Toni-d-e-v on GitHub (Jan 28, 2023). # Docker ``` 70d69ab367cf vaultwarden/server "/usr/bin/entry.sh /…" 44 minutes ago Up 30 minutes (healthy) 80/tcp, 0.0.0.0:3012->3012/tcp, :::3012->3012/tcp, 0.0.0.0:8088->8080/tcp, :::8088->8080/tcp vaultwarden ``` # Apache2 conf ``` <VirtualHost *:80> ServerName my.domain.com #SSLCertificateFile ${SSLCERTIFICATE} #SSLCertificateKeyFile ${SSLKEY} #SSLCACertificateFile ${SSLCA} #${SSLCHAIN} ErrorLog /home/ubuntu/dockers/vaultwarden/bitwarden-error.log CustomLog /home/ubuntu/dockers/vaultwarden/bitwarden-access.log combined # RewriteEngine On # RewriteCond %{HTTP:Upgrade} =websocket [NC] # RewriteRule /notifications/hub(.*) ws://0.0.0.0:3012/$1 [P,L] RewriteEngine On RewriteCond %{HTTP:Upgrade} websocket [NC] RewriteCond %{HTTP:Connection} upgrade [NC] RewriteRule ^/?(.*) "ws://127.0.0.1:3012/$1" [P,L] ProxyPass / http://127.0.0.1:8080/ ProxyPreserveHost On ProxyRequests Off RequestHeader set X-Real-IP %{REMOTE_ADDR}s # Add this line if your url attributes are reported back as http://... : RequestHeader add X-Forwarded-Proto https RewriteCond %{SERVER_NAME} =my.domain.com RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost> ``` # Issue ![image](https://user-images.githubusercontent.com/62844491/215263223-cb6aac9d-e5ea-4eda-a89c-0810327899fa.png) HTTPS Is enabled and here are the logs # Custom logs! ``` [Sat Jan 28 11:01:49.607972 2023] [proxy:error] [pid 35283] (111)Connection refused: AH00957: http: attempt to connect to 0.0.0.0:8080 (0.0.0.0) failed [Sat Jan 28 11:01:49.608007 2023] [proxy_http:error] [pid 35283] [client 93.231.123.17:39088] AH01114: HTTP: failed to make connection to backend: 0.0.0.0, ``` # Server I'm using amr64 server that runs docker, its cloud instance of oracle and I got no issues running nextcloud

OVERLORD closed this issue

2026-02-05 01:03:55 +03:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1484