this post was submitted on 19 Jan 2024
12 points (87.5% liked)

Selfhosted

40173 readers
832 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
12
how to access nextcloud outside LAN? (kbin.social)
submitted 10 months ago by [email protected] to c/[email protected]
23 comments fedilink hide all child comments
 

ive anabled a port forward on port 80 (TCP/UDP) to my server, but i still cant acess it. i know its unsafe to just open a port like that, this is temporary, just wanna see if it works. ill put a reverse proxt and https on it later

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 9 months ago (1 children)

Absolutely do not expose your server on port 80. Http is unencrypted, you'd be sending your login credentials in plaintext across the open internet. That is Very Bad™. If you own a domain name, you can set up a letsencypt cert fairly easily for free. Then you could expose 443 and at least your traffic will be encrypted in transit. It won't solve the other potential issues of exposing your instance like brute force or ddos attacks, but I'd consider it a bare minimum.

If you use a VPN like many others are suggesting it won't matter as much because the unencrypted traffic never leaves your local network.

[–] [email protected] 3 points 9 months ago (1 children)

As a side note: you not technically need a domain or a let's encrypt certificate to enable https. As a test you can create your own certificate, and use that for https (snake-oil certificate).

This is not appropriate for longer-term usage. If you want to run websites on the Internet long-term, you should buy a domain and get a lets-encrypt certificate.

[–] [email protected] 1 points 9 months ago (1 children)

Technically true but I wouldn't suggest using a self signed cert on the internet under any circumstances.