Skip to content
New issue

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

Cannot run SyncTybe behind an Apache reverse proxy #60

Open
RolandMarchand opened this issue Mar 1, 2025 · 2 comments
Open

Cannot run SyncTybe behind an Apache reverse proxy #60

RolandMarchand opened this issue Mar 1, 2025 · 2 comments

Comments

@RolandMarchand
Copy link

Users are not able to connect to SyncTube when the service runs behind an Apache reverse proxy.

The application works when entering the raw address and port number (via IP or domain name).

Here is my Apache configuration:

<VirtualHost *:80>
  ServerName sync.lazarusoverlook.com
  Redirect permanent / http://sync.lazarusoverlook.com/
  ProxyPreserveHost On
  ProxyPass / http://40.233.79.250:4200/
  ProxyPassReverse / http://40.233.79.250:4200/
</VirtualHost>

Here is a screenshot of the instant disconnection:
Image

Environment

  • OS: Oracle Linux Server 8.10 (ARM64)
  • Kernel: 5.15.0-305.176.4.el8uek.aarch64
  • Httpd: 2.4.37
  • SyncTube: f267adf
@RblSb
Copy link
Owner

RblSb commented Mar 1, 2025

Server tries connection to wss://sync.lazarusoverlook.com/ and fails. Probably you need to also configure wss port (443) on your domain proxy?

Don't have experience with apache, so idk, there is some AI hints about further ws configuration as reference
https://www.perplexity.ai/search/apache-reverse-proxy-cannot-up-vBChY0oeQgypNpawtkspuw

I only know that cloudflare https proxy works, so this is probably about correcting configuration too.

@SimplisticGH
Copy link

Here's an example from my previous setup before I switched to nginxproxymanager

<VirtualHost *:443>
        ServerName your.domain.com
        AllowEncodedSlashes On
        ProxyPreserveHost on
        RewriteEngine on
        RewriteCond %{HTTP:Upgrade} websocket [NC]
        RewriteCond %{HTTP:Connection} upgrade [NC]
        RewriteRule .* "ws://localhost:4200%{REQUEST_URI}" [P]
        ProxyRequests Off
        ProxyPass / http://localhost:4200/
        ProxyPassReverse / http://localhost:4200/

        SSLCertificateFile /etc/letsencrypt/live/your.domain.com/fullchain.pem
        SSLCertificateKeyFile /etc/letsencrypt/live/your.domain.com/privkey.pem
</VirtualHost>

You'll have to turn on a few modules, but I never remember which ones. I know for sure you need rewrite and websockets in my example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants