this post was submitted on 27 Aug 2025
41 points (100.0% liked)

Selfhosted

60734 readers
210 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] humanoidchaos@lemmy.cif.su 1 points 10 months ago* (last edited 10 months ago) (1 children)

I was able to run the server properly after building it with ./build -g. I can connect if I select the local server and therefore have localhost for ip address and ip management in the config.

If possible, I'd like to find out where I can put my VPN's internal IP address (assuming that's what I need) so I could have the server listen on that interface and let people connect to my server from the outside.

Thanks again for all your help and your contributions to this project.

[โ€“] ryannathans@aussie.zone 1 points 10 months ago

You shouldn't need to put your VPN IP anywhere in the server, by default I'm pretty sure it listens on all interfaces. Just the client config I imagine is sufficient