support@lune.dev

Want to use over 200+ MCP servers inside your coding tools like Cursor?

Asked 1 month ago by MercurialCommander527

From Django Community

Why isn’t my Django app served by Apache accessible via OpenVPN?

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

Hello,

I’m encountering an issue where my Django application served by Apache isn’t accessible over my OpenVPN connection, even though a static HTML page on a similar virtual host works fine. My goal is to enable access to the Django server on a local network through a mobile device using VPN.

I have tested the VPN with Apache to display a simple HTML file. For example, I set up a virtual host as follows:

APACHE
<VirtualHost 10.124.0.2:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www/test.com/public_html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
ServerName 10.124.0.2
ServerAlias 10.124.0.2

This configuration works; when the VPN is active, entering the IP in the browser loads the test page successfully.

I then created a virtual host for my Django project with the following configuration:

APACHE
<VirtualHost 10.124.0.2:80>
ServerAdmin webmaster@localhost
ServerName 10.124.0.2
ServerAlias 10.124.0.2

WSGIDaemonProcess classicoutdoor processes=2 threads=12 python-path=/var/www/webapp/work_management:/var/www/webapp/myprojectenv/lib/python3.12/site-packages
WSGIProcessGroup classicoutdoor
WSGIScriptAlias / /var/www/webapp/work_management/work_management/wsgi.py

BASH
# This alias makes serving media files possible.

Alias /media/ /var/www/webapp/media/
<Directory /var/www/webapp/media>
Require all granted

Alias /static/ /var/www/webapp/work_management/staticfiles/

APACHE
<Directory /var/www/webapp/work_management/work_management>
<Files wsgi.py>
Require all granted
</Files>
</Directory>

LogLevel warn

PROJECT_NAME is used to separate the log files of this application

ErrorLog ${APACHE_LOG_DIR}/classicoutdoor_error.log
CustomLog ${APACHE_LOG_DIR}/classicoutdoor_access.log combined

BASH
When I attempt to connect the connection times out. The URL seems to redirect to my login page but never fully loads.

If I change the virtual host to use the public IP and update settings.py accordingly, everything works as expected—just not via the local VPN network.

Any ideas on what might be causing this issue with the WSGI configuration in the VPN setup?

Thanks for your help!

Comments 0

•

Answers 1

•

1 Answer

Answer by StackOverflow TychoAI Agent • 9 days ago

Django Application Access Issues Over OpenVPN

Based on your configuration and the issue you're experiencing, there are several potential causes for why your Django application isn't accessible over OpenVPN while a static HTML page works fine.

Possible Issues and Solutions

1. ALLOWED_HOSTS Setting

The most likely issue is that your Django settings.py file doesn't include the VPN IP address in the ALLOWED_HOSTS setting:

PYTHON
# Make sure your settings.py includes the VPN IP
ALLOWED_HOSTS = ['10.124.0.2', 'your-public-ip', 'localhost', '127.0.0.1']

2. Apache Configuration Issues

Your Apache configuration has some syntax errors and incomplete directives:

APACHE
<VirtualHost 10.124.0.2:80>
    ServerAdmin webmaster@localhost
    ServerName 10.124.0.2
    ServerAlias 10.124.0.2

    WSGIDaemonProcess classicoutdoor processes=2 threads=12 python-path=/var/www/webapp/work_management:/var/www/webapp/myprojectenv/lib/python3.12/site-packages
    WSGIProcessGroup classicoutdoor
    WSGIScriptAlias / /var/www/webapp/work_management/work_management/wsgi.py

    # Media files
    Alias /media/ /var/www/webapp/media/
    <Directory /var/www/webapp/media>
        Require all granted
    </Directory>

    # Static files
    Alias /static/ /var/www/webapp/work_management/staticfiles/
    <Directory /var/www/webapp/work_management/staticfiles>
        Require all granted
    </Directory>

    <Directory /var/www/webapp/work_management/work_management>
        <Files wsgi.py>
            Require all granted
        </Files>
    </Directory>

    LogLevel warn
    ErrorLog ${APACHE_LOG_DIR}/classicoutdoor_error.log
    CustomLog ${APACHE_LOG_DIR}/classicoutdoor_access.log combined
</VirtualHost>

Note that I've added the missing closing tags and the permissions for the static files directory.

3. WSGIApplicationGroup Setting

When running multiple Django applications, you might need to set the application group:

APACHE
WSGIApplicationGroup %{GLOBAL}

4. Check Error Logs

Examine your Apache error logs for specific issues:

BASH
tail -f /var/log/apache2/classicoutdoor_error.log

5. Network/Firewall Issues

Ensure that:

The VPN server is correctly routing traffic to the Django server
No firewall rules are blocking the connection
The Django server is listening on the VPN IP address

6. Django Redirects

If your Django application is redirecting to a different domain or IP than the one you're accessing it through, this could cause issues. Check your Django settings for any hardcoded URLs or redirects.

Recommended Steps

Fix your Apache configuration as shown above
Add the VPN IP to your Django ALLOWED_HOSTS
Restart Apache: sudo systemctl restart apache2
Check the error logs for any specific issues
Test with a simple Django view that doesn't require authentication or redirects

If these steps don't resolve the issue, examining the Apache and Django error logs will provide more specific information about what's happening when you try to access the application over VPN.

Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?

No comments yet.

Discussion