Does anybody happen to know of a guide that will tell me how to get , when receiving requests on port 443 for a certain directory and subdirectories (e.g. /caldav/*), to proxy it to the server listening on port 80?

This needs to coexist with nginx proxying all other requests NOT for that path and subdirectories to a different port (Pleroma, actually).

@deutrino You can't forward from 443 -> 80. It breaks SSL. You *can* forward from 80 -> 443, though:

server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
return 301 https://$host$request_uri;
}

@deutrino If you're talking about proxying to another server *behind* the nginx instance (i.e. nginx terminates SSL and the other server just hosts the actual service)...well that's easy and any basic proxy examples should work.

Follow

@john Yeah, the possible wrinkle is that I already have it proxying traffic for Pleroma, so it needs to be only proxying stuff aimed at (for example) /gitea and below, and let everything else be handled by the other config.

Sign in to participate in the conversation
Mastodon

Fast, secure and up-to-date instance, welcoming everyone around the world. Join us! 🌍
Up since 04/04/2017. ✅

Why should you sign up on mstdn.io?

This instance is not focused on any theme or subject, feel free to talk about whatever you want. Although the main language is english, we accept every single language and country.

We're connected to the whole ActivityPub fediverse and we do not block any foreign instance nor user.

We do have rules, but the goal is to have responsible users.

The instance uses a powerful server to ensure speed and stability, and it has good uptime. We follow state-of-the-art security practices.

Also, we have over 300 custom emojis to unleash your meming potential!


Looking for a Kpop themed instance? Try kpop.social