Problem with self hosting setup

I followed the 30 min setup. Taiga is available locally, no problem. I need it to be accessible from the internet though. Thus I set up an Apache virtual host with a reverse proxy setup to nginx. With this I can access taiga but get only an erroneus page. The developer version of the browser tells me that there are 4 ‘Failed to load resource’ errors: theme-taiga.css, spinner-circle.svg, app-loader.js and again, theme-taiga.css. I have checked the proxy settings and they seem ok. There are no error messages neither in the apache2 error log nor in the nginx error log. Both access logs show normal access. I am pretty much hitting the wall. Is there some documentation I could read about making an install which runs perfectly local to make available from the internet?

Are you able to successfully open the taiga page without the proxy?
something like

Also post your vhost config for the reverse proxy.

It should look something like this (with https/ssl)

<VirtualHost *:443>
  ErrorLog /var/log/apache2/proxiedhosts-ssl_error.log
  # Possible values include: debug, info, notice, warn, error, crit,
  # alert, emerg.
  LogLevel warn
  CustomLog /var/log/apache2/access-ssl.log combined
  ## ReWrite for WebSocket
  RewriteEngine On
  RewriteCond %{HTTP:Upgrade} =websocket [NC]
  RewriteRule /(.*)           ws://$1 [P,L]
  RewriteCond %{HTTP:Upgrade} !=websocket [NC]
  RewriteRule /(.*) $1 [P,L]
# Use mod_proxy_html to rewrite URLs
  SetOutputFilter proxy-html
  ProxyPass /
  ProxyPassReverse /
  RequestHeader unset  Accept-Encoding
  SSLEngine on
  SSLProxyEngine On
  # LetsEncrypt certificate
  SSLCertificateFile   /etc/letsencrypt/live/
  SSLCertificateKeyFile /etc/letsencrypt/live/

1 Like

If, as you mention, taiga works perfectly on localhost, the problem is in the proxy pass that you are trying to make with Apache. ​The browser error indicates that the proxy pass cannot serve the files, probably because Apache is not reaching localhost:9000.

We have an example in the manual that you followed to do what you want using nginx and the example that @jcain proposes looks very good too. Personally we prefer nginx over Apache to act as a reverse proxy, but both should work perfectly if they are properly configured.