Just don't set 'localhost' as argument to '--server-name'. Try using:
--server-name 127.0.0.1.nip.io --allow-localhost
Try accessing it with both http://127.0.0.1.nip.io and http://localhost
<http://localhost/>.
Using 'localhost' is going to cause issues with Apache because it usually
doesn't allow/honour use of 'localhost' as ServerName in a VirtualHost.
If you don't know what nip.io <http://nip.io/> is, go to:
https://nip.io/ <https://nip.io/>
to find out.
Graham
> On 29 Jul 2020, at 7:54 am, Licht Artig <[email protected]> wrote:
>
> Hi Graham,
>
> thanks for your quick reply! Right now I'm simply trying out things, so the
> certificate is not trusted anyways. I tried adding your option
> '--allow-localhost', but the error persists. So no matter if I connect to
> HTTP on port 8000 or HTTPS on port 8443, I get the same error 403.
>
> Do you have any idea what I'm doing wrong?
>
> Best
>
> Am Di., 28. Juli 2020 um 23:47 Uhr schrieb Graham Dumpleton
> <[email protected] <mailto:[email protected]>>:
> If you are using a certificate, the --server-name should be the name of the
> host the certificate is for. A secure site and certificate shouldn't be set
> up for localhost.
>
> If for some reason you do need to be able to access a secure site via
> localhost, even though that would then mean the certificate wouldn't be
> trusted, try adding the option '--allow-localhost'.
>
> The help string for the option is:
>
> Flag indicating whether access via localhost should still be allowed
> when a server name has been specified and a name based virtual host has been
> configured.
>
> Graham
>
>> On 29 Jul 2020, at 4:25 am, Licht Artig <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi,
>>
>> I'm currently trying to configure mod_wsgi-express to run a website I'm
>> developing in HTTP and HTTPS. After struggling for some time, I noticed that
>> the problem also occurs for the demo-page that comes with the tool.
>> So let me describe the error in more detail with this minimal-example.
>>
>> If I run the command
>> mod_wsgi-express start-server
>> I can acces the demo page (the one with the "malt whiskey") without
>> problems, but things go wrong when I add HTTPS.
>>
>> So I'm starting the server with
>> mod_wsgi-express --https-port 8443
>> --ssl-certificate-file=/home/pi/keys/server.crt
>> --ssl-certificate-key-file=/home/pi/keys/server.key --server-name localhost
>> and no errors come up initally.
>>
>> But if I try to access the site either at its unencrypted location at
>> http://localhost:8000/ <http://localhost:8000/> or the encrypted site at
>> https://localhost:8443/ <https://localhost:8443/>, I get the following error:
>> 403 Forbidden - You don't have permission to access this resource.
>> Addtionally I printed out the error-log and found the following error
>> AH01630: client denied by server configuration:
>> /tmp/mod_wsgi-localhost:8000:1000/htdocs/
>>
>> I am guessing there is probably a very simple fix for this, but I can't get
>> my head around it. So any help is greatly appreciated! Thanks in advance!
>>
>> PS: I tried this both on my Ubuntu computer as well as my RaspberryPi. The
>> error is the same.
>>
>> --
>> 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]
>> <mailto:[email protected]>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/modwsgi/02cb86f5-c7b2-4aa7-bff6-c041a5d46e20o%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/modwsgi/02cb86f5-c7b2-4aa7-bff6-c041a5d46e20o%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]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/modwsgi/77C55ECF-A34A-4AC0-8C8B-CBC5527D2BDC%40gmail.com
>
> <https://groups.google.com/d/msgid/modwsgi/77C55ECF-A34A-4AC0-8C8B-CBC5527D2BDC%40gmail.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]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/modwsgi/CA%2B%2BvfrsJQHkmTyDrYxoMOAP2mA82MLQ6Mw0GsG8V11ekXgrQUQ%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/modwsgi/CA%2B%2BvfrsJQHkmTyDrYxoMOAP2mA82MLQ6Mw0GsG8V11ekXgrQUQ%40mail.gmail.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/71B83BCE-68E9-4F69-93E1-152FE12F992E%40gmail.com.
