Apache is running just fine. We run Squirrelmail and sendmail for legacy 
email purposes and also have a few web pages running ok. We do enable SSL, 
e.g.,:
Listen 443 https
SSLEngine on
And enabled UserDir:
UserDir public_html

Since there are some logs being produced by mod_wsgi as shown in the log 
snippets, and mod_wsgi-express start-server works, I agree there is 
something within the Apache configuration. We do have some RewriteEngine 
rules:
RewriteEngine on
RewriteCond %{SERVER_NAME} =oursubdomain.ourschool.edu [OR]
RewriteCond %{SERVER_NAME} =*. oursubdomain.ourschool.edu
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

We do have a separate tool called sendmailanalyzer 
<https://github.com/darold/sendmailanalyzer> running just fine as well, 
which works on port 443.

So could some of these settings be causing any port I try to not be 
available? 

Also wanted to show a (different) port in use with mod_wsgi-express:
netstat -ln|grep 8987
tcp6       0      0 :::8987                 :::*                    LISTEN  
   
unix  2      [ ACC ]     STREAM     LISTENING     222147816 
/tmp/mod_wsgi-localhost:8987:0/wsgi.25662.u16836.1.sock

On Wednesday, October 30, 2019 at 9:50:22 PM UTC-4, Graham Dumpleton wrote:
>
> If port 8000 is refusing connections, that shouldn't be related to the 
> WSGI application as it is Apache that handles connections. So Apache would 
> appear not to be running or you have mucked up something in the Apache 
> configuration to disable the VirtualHost.
>
> On 31 Oct 2019, at 12:37 am, Robert Kudyba <[email protected] 
> <javascript:>> wrote:
>
> Good thought. But I tried changing to the corresponding user & group, and 
> still no luck. Even added the user to the apache group just to make sure. 
> Logs just show this:
> [Wed Oct 30 09:33:32.043767 2019] [wsgi:info] [pid 3980:tid 
> 140481291338048] mod_wsgi (pid=3980): Attach interpreter ''.
> [Wed Oct 30 09:33:32.047098 2019] [wsgi:info] [pid 3980:tid 
> 140481291338048] mod_wsgi (pid=3980): Imported 'mod_wsgi'.
> [Wed Oct 30 09:33:32.047324 2019] [wsgi:debug] [pid 3980:tid 
> 140481237260032] src/server/mod_wsgi.c(9068): mod_wsgi (pid=3980): Started 
> thread 1 in daemon process 'upload_pictures2'.
> [Wed Oct 30 09:33:32.047400 2019] [wsgi:debug] [pid 3980:tid 
> 140481245652736] src/server/mod_wsgi.c(9068): mod_wsgi (pid=3980): Started 
> thread 0 in daemon process 'upload_pictures2'.
> [Wed Oct 30 09:33:32.047411 2019] [wsgi:debug] [pid 3980:tid 
> 140481212081920] src/server/mod_wsgi.c(9068): mod_wsgi (pid=3980): Started 
> thread 4 in daemon process 'upload_pictures2'.
> [Wed Oct 30 09:33:32.047440 2019] [wsgi:debug] [pid 3980:tid 
> 140481228867328] src/server/mod_wsgi.c(9068): mod_wsgi (pid=3980): Started 
> thread 2 in daemon process 'upload_pictures2'.
> [Wed Oct 30 09:33:32.047441 2019] [wsgi:debug] [pid 3980:tid 
> 140481220474624] src/server/mod_wsgi.c(9068): mod_wsgi (pid=3980): Started 
> thread 3 in daemon process 'upload_pictures2'.
>
> And curl fails:
>
> curl http://127.0.0.1:8000/upload
> curl: (7) Failed to connect to 127.0.0.1 port 8000: Connection refused
>
> curl http://127.0.0.1:8000
> curl: (7) Failed to connect to 127.0.0.1 port 8000: Connection refused
>
> On Tuesday, October 29, 2019 at 10:22:03 PM UTC-4, Graham Dumpleton wrote:
>>
>> When you run 'mod_wsgi-express start-server' it runs as you and is not 
>> the same. 
>>
>> Apache is going to run it as the Apache user, which may not have the same 
>> access. 
>>
>> Change user and group in: 
>>
>> WSGIDaemonProcess upload_pictures2 user=apache group=apache threads=5 
>>
>> to what user has access to the directory to write files. 
>>
>> Graham 
>>
>> > On 30 Oct 2019, at 1:19 pm, Robert Kudyba <[email protected]> wrote: 
>> > 
>> > Absolutely. Image uploads work with mod_wsgi-express start-server. 
>> > 
>> > -- 
>> > 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 [email protected]. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/modwsgi/455d6200-2a0b-4ef2-92dd-15ed6f8c819d%40googlegroups.com
>> . 
>>
>>
> -- 
> 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 [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/modwsgi/a3daa6a9-4c18-4e5e-9410-b5a71e7a7fee%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/modwsgi/a3daa6a9-4c18-4e5e-9410-b5a71e7a7fee%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/modwsgi/e7457687-91d1-46c6-adbf-2cb1c401ec9d%40googlegroups.com.

Reply via email to