Setup behind Traefik

[xploz1on]

I am currently running my own instance to admin docker containers and I have a Traefik reverse proxy. I am running this is a cloud server (Using Cosmos Cloud).

EDITED

I am now able to log into the webmin instance.

Still getting the following error:

Mar 24 12:20:59 - DEBUG - Waiting 299.94 seconds until next execution.
wireguard-webadmin          | [24/Mar/2025 12:21:01] "GET /api/cron_check_updates/ HTTP/1.1" 200 27
wireguard-webadmin          | Invalid HTTP_HOST header: '172.18.0.2:8000'. You may need to add '172.18.0.2' to ALLOWED_HOSTS.
wireguard-webadmin          | Traceback (most recent call last):
wireguard-webadmin          |   File "/usr/local/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
wireguard-webadmin          |     response = get_response(request)
wireguard-webadmin          |                ^^^^^^^^^^^^^^^^^^^^^
wireguard-webadmin          |   File "/usr/local/lib/python3.12/site-packages/django/utils/deprecation.py", line 128, in __call__
wireguard-webadmin          |     response = self.process_request(request)
wireguard-webadmin          |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
wireguard-webadmin          |   File "/usr/local/lib/python3.12/site-packages/django/middleware/common.py", line 48, in process_request
wireguard-webadmin          |     host = request.get_host()
wireguard-webadmin          |            ^^^^^^^^^^^^^^^^^^
wireguard-webadmin          |   File "/usr/local/lib/python3.12/site-packages/django/http/request.py", line 151, in get_host
wireguard-webadmin          |     raise DisallowedHost(msg)
wireguard-webadmin          | django.core.exceptions.DisallowedHost: Invalid HTTP_HOST header: '172.18.0.2:8000'. You may need to add '172.18.0.2' to ALLOWED_HOSTS.
wireguard-webadmin          | Bad Request: /
wireguard-webadmin          | Invalid HTTP_HOST header: '172.18.0.2:8000'. You may need to add '172.18.0.2' to ALLOWED_HOSTS.

Is this because it is looking for the proxy you recommended using?
Thanks!!

EDIT:
Correct me if I'm wrong but. Can I manage multiple Wireguards server in different servers with one instance?

[eduardogsilva]

Hello @xploz1on,

Your logs show that Django is rejecting the internal IP ('172.18.0.2:8000') in the HTTP_HOST header, which indicates that the reverse proxy isn’t forwarding the expected domain name. In a reverse proxy setup, the proper behavior is for the proxy to pass along the original host header from the client.

For example, with Nginx you would include:

proxy_set_header Host $host;

Traefik’s default behavior is similar—passHostHeader is set to true by default—so it should forward the correct host header. If you’re seeing the internal IP instead, it’s likely due to one of the following:

• The Docker labels for Traefik might not be correctly configured to define the expected host rule.
• Your Cosmos Cloud environment might be modifying the network behavior or overriding the forwarded headers.

While you could temporarily set SERVER_ADDRESS=172.18.0.2:8000 in your .env file to bypass the error, this is not a recommended solution for production since it only masks the underlying configuration issue. The best approach is to adjust your Traefik (or Cosmos Cloud) configuration so that the correct host header is forwarded to your Django app, ensuring it matches the domain defined in your ALLOWED_HOSTS.

This should resolve the error and maintain the integrity of your production environment.

I would also strongly recommend using Nginx after your traefik. This is the preferred way of running wireguard_webadmin. Nginx would serve the static files and forward application requests to Django. If you run the version without Nginx, you will be running Django in DEBUG mode, which is not recommended for production.

Cheers!

[xploz1on]

Thank you for your answer.
Will be running some tests tonight.

So my end goal is having several server in different country/providers and afaik this will allow me to manage all of them with just one admin panel correct?

Thank you

[eduardogsilva]

Hello @xploz1on

I'm sorry but I'm afraid that it's not exactly that.
You can run multiple wireguard instances (interfaces) on the same server. It's not designed to multi server deployment.

Cheers

[eduardogsilva]

Hello @xploz1on

I've started to work in Multi-Server support.
If you are still interested, I would love to hear your feedback about your needs and your usage case.

Please check the issue #86

Cheers!