Error cannot load certificate "/etc/letsencrypt/live/domainname/fullchain.pem"

[9peppe]

I think it’s fine that way

[Encrypt1919]

I’ve checked my page again and I have a lot of errors, for example: https://check-your-website.server-daten.de/?q=gotobot.co

Do you think I should work on them all or?

[9peppe]

I would direct my attention to

• “Fatal error: Nameservers mit different SOA Serial Numbers”; and
• “Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.”

the others, you choose.

[Encrypt1919]

Thanks.

I’m wondering now for my default.conf file does it make sense to write code like this if I want to accept only requests that are sending a proper token?

location = /hotel { rewrite ^ /hotel/ redirect; }
location /hotel {
    #proxy_pass    http://rasa;
    rewrite /hotel/(.*) /$1 break;
    proxy_pass    http://rasa/webhooks/rest/webhook?token=;
    include       partials/common.conf;
    #include       partials/ssl.conf;

}

Or should I remove “?token=” ?

[9peppe]

nginx can’t know if a token is proper. your application needs to send the proper http 4xx error response.

if nginx can proxy_pass inside a querystring, I don’t know.

[Encrypt1919]

So I don’t have to specify the “?token=” and rather send it in post request and accept it with backend logic?

[9peppe]

I have no idea. This only has to do with your application.

[Encrypt1919]

Rasa has built in auth token param and I just have to add this when running docker-compose up:

rasa run --auth-token thisismysecret

But I do not know how to enable this in config of SSL?