Skip to content

Setting up Reverse Proxy with SWAG? #48

Description

@beboprocky

Example: https://shareme.domain.com

Setup (using *.domain.com as an example):
Docker Compose
frontend:
environment:
POCKETBASE_URL: https://shareme-pb.domain.com

I then go to shareme-pb.domain.com/_/
I create an admin account.
I create a user account.
I go to Settings > Application > and set the following:
Application name: shareme
Application url: https://shareme.domain.com (same url as above but without "-pb")

Both domains work. But I am unable to login or sign up for a new account on the front end. Clicking "Login" does nothing. Clicking "Sign Up" gives me a 500 error.

I'm a little confused on the setup at this point.. The documentation says to forward "/api and /_ to the PocketBase backend" and "the rest of the traffic including /_next to the frontend". I saw in a Reddit post this possible to do with using subdomains, but I'm not sure what subdomains should be pointed to which domains or IP addresses. I don't believe SWAG can forward paths, so subdomains might be my only route.

Also, would the backend in this case be "shareme-pb.domain.com" or would I need to forward api and /_ to something else?

Thank you for the help if at all possible. I'm a self-host hobbyist so a few concepts do go over my head. I was able to get it working locally without a reverse proxy and this seems to be exactly what I was looking for. I appreciate the hard work that's gone into this project. It was definitely needed in the self-hosting space.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions