Skip to content

Document config.json when using reverse proxy #819

Open

Description

@jernst

I assume this is the intended setup?

  • If I run Apache on port 80 + 443
  • and I run sold-server at port 5001
  • and my hostname is example.com
    then the config.json file has those entries:
{
  "port": "5001",
  "serverUri": "https://example.com",
}

Is that right?

Activity

  1. kjetilk commented on Oct 2, 2018

    @kjetilk
    Member

    Yes, that looks about right. I have a slightly different setup where I have HAProxy on a different machine than where I have solid-server, but it is essentially the same thing.

    So, the reason I didn't write this in the documentation on the solid site was that there is a gazillion ways to do this, depending on what you choose for frontend, and whether it is on a different box. We do need more complete documentation, but it is complex enough as it is, so I was wary of introducing this is as well.

  2. melvincarvalho commented on Oct 2, 2018

    @melvincarvalho
    Contributor
  3. jernst commented on Oct 2, 2018

    @jernst
    Author

    I saw those notes on the wiki, but the core of my question -- about the config file -- isn't addressed there. Specifically whether the port also needs to be on serverUri.

  4. kjetilk commented on Oct 2, 2018

    @kjetilk
    Member

    @jernst serverUri is what the world should see, so if you're proxying it, then it shouldn't have the port.

  5. added and removed
    triageIssues that need team review
    on Nov 6, 2018
  6. added
    good first issueAn issue that should be quite easy for newcomers to fix
    priority-lowto be used for lower priority issues and pull requests
    on Nov 6, 2018
  7. Saifjafri212213 commented on Oct 10, 2026

    @Saifjafri212213

    Hi, I'd like to work on documenting the config.json setup for reverse proxies. Could you please assign it to me?

  8. bourgeoa commented on Oct 10, 2026

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

Metadata

Metadata

Labels

documentationgood first issueAn issue that should be quite easy for newcomers to fixpriority-lowto be used for lower priority issues and pull requests

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions