Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
Ohh ok testing right away!, thanks -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+unsubscr...@googlegroups.com. To post to this group, send email to

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
BTW the things that did not show anything about the 443 were when mod_wsgi was off. Because when I restart the mod_wsgi I can see the port being used by mod_wsgi when use > sudo netstat -tulpn also when I run > lsof -i :443 > -- You received this message because you are subscribed

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Graham Dumpleton
Missed it. Don't set: --port=443 If you want HTTPS only with redirect from port 80 to 443 use: --port 80 --https-port=443 --https-only Graham > On 22 Feb 2018, at 2:30 pm, Rafael Karosuo wrote: > > Ok, the apache instance that where active (for the

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
Ok, the apache instance that where active (for the cpanel/whm I suppose) is already disabled, I used > > WHM >> Home >> Service Configuration >> Service Manager Because using: > /usr/sbin/apachectl stop was temporal, cpanel/whm was looking for that process and if it was stopped, it can be

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Graham Dumpleton
> On 22 Feb 2018, at 1:37 pm, Rafael Karosuo wrote: > > Stop mod_wsgi-express and do the same thing. > curl -v https://mytademex.com > * About to connect() to mytademex.com port 443 (#0) > * Trying 127.0.0.1... Connection refused > * Trying 108.179.223.220...

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
I restarted the mod_wsgi and ran curl -v https://mytademex.com from my ubuntu machine. I have this result > * Rebuilt URL to: https://mytademex.com/ > * Trying 108.179.223.220... > * Connected to mytademex.com (108.179.223.220) port 443 (#0) > * found 148 certificates in

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
> > Stop mod_wsgi-express and do the same thing. > curl -v https://mytademex.com * About to connect() to mytademex.com port 443 (#0) * Trying 127.0.0.1... Connection refused * Trying 108.179.223.220... Connection refused * couldn't connect to host * Closing connection #0 curl: (7) couldn't

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Graham Dumpleton
Stop mod_wsgi-express and do the same thing. Does it say can't even connect, or does it still connect? Do you have any environment variables that may be set which is causing a proxy to be used? If you have 'telnet' on the host, what happens if you type 'telnet mytademex.com

[modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
Oh ok, I ran these one. > python manage.py runmodwsgi --setup-only --port=443 --user mytademe > --group mytademe --server-root=/etc/mod_wsgi-443 --server-name > mytademex.com --ssl-certificate /etc/pki/tls/certs/mytademex --https-only > --startup-log --access-log I have a VPS, so I did

[modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
BTW, startup_log does not have anything at all. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to modwsgi+unsubscr...@googlegroups.com. To post to this group, send

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Graham Dumpleton
> On 22 Feb 2018, at 12:48 pm, Rafael Karosuo wrote: > > I just added the part of --ssl-certificate, now running > > python manage.py runmodwsgi --setup-only --port=443 --user myuser --group > mygroup --server-root=/etc/mod_wsgi-443 --server-name mytademex.com >

[modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-21 Thread Rafael Karosuo
I just added the part of *--ssl-certificate*, now running python manage.py runmodwsgi --setup-only --port=443 --user myuser --group > mygroup --server-root=/etc/mod_wsgi-443 --server-name mytademex.com > --ssl-certificate-file /etc/pki/tls/certs/mytademex.crt > --ssl-certificate-key-file

[modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-15 Thread Rafael Karosuo
I'm

Re: [modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-14 Thread Graham Dumpleton
Your BASE_DIR value in your settings file is possibly wrong if you have reorganised how settings are kept from normal second level to third level directory. If you run: python manage.py diffsettings what does it show for BASE_DIR? Is it the directory above your project directory? Also,

[modwsgi] Re: When use mod_wsgi.../apachectl status, Error loading https://localhost:443/server-status: SSL error

2018-02-13 Thread Rafael Karosuo
I started testing the information you gave me. I'm stuck with an import error since I used the server-root option. I assumed that doing something like > export PYTHONPATH='my_project_container_dir/my_parent_module' would be enough before doing the *apachectl start* command, but it is not