humanoidchaos

joined 5 days ago
[–] humanoidchaos@lemmy.cif.su 2 points 8 hours ago

Sorry, it should be up again now.

I've updated the post with the instructions. I don't really plan on hosting this for a long period of time, at least not in this state.

I hope some people have gotten some use out of it.

[–] humanoidchaos@lemmy.cif.su 4 points 1 day ago (1 children)

Thanks. This is new to me and I'm going to be looking into it.

No problem.

For my VPN, it tells me the forwarded port in the software's GUI. I'm not sure how to find it out through the command line.

[–] humanoidchaos@lemmy.cif.su 11 points 1 day ago (27 children)

Thanks.

It's my understanding that https provides encryption for the data sent between you and the server. If you're not sending any sensitive data, then the encryption shouldn't be necessary.

Don't get me wrong, encryption is great even when it isn't necessary. For my demonstration purposes though, I chose not to include it.

I also believe it's possible to set up HTTPS encryption without a domain name, but it might result in that "we can't verify the authenticity of this website" warning in web browsers due to using a self-signed certificate.

It's not dumb at all! Don't be afraid to ask. I'm not an expert and still learning myself.

The VPN is running on the same machine that I am hosting the website on. There may be some configuration you can do to perhaps have the connection routed through your raspberry pi with a VPN running on it to the machine that's hosting the website, but I'm not sure how.

Otherwise, you should be able to at the very least run the entire setup on a raspberry pi.

73
How to selfhost with a VPN (95.181.238.114:49703)
submitted 1 day ago* (last edited 1 hour ago) by humanoidchaos@lemmy.cif.su to c/selfhosted@lemmy.world
 

These are some quick n' dirty instructions so people can get up and running fast.

I wish I had known this was possible sooner.

Instructions:

Check that your VPN supports port forwarding and you have it enabled.

Grab your VPN's internal IP with ip a

Find the interface for your VPN. For me it's called tun0.

Open up /etc/nginx/nginx.conf

You can back it up, or comment everything out, or pick what's necessary. Here's what my file looks like.

	worker_processes  1;
	include modules.d/*.conf;

	events {
		worker_connections  1024;
	}
	http {
		server {
			listen [VPN INTERNAL IP]:[VPN FORWARDED PORT];
			server_name  localhost;
			location / {
				root '[ABSOLUTE PATH TO YOUR WEBSITE ROOT FOLDER]';
				index index.html; # Relative to your website root.
			}
		}
	}

Make sure your permissions are correct. For me, the 'other' group needs read permissions to the root folder, including where it's mounted.

Start nginx with systemctl start nginx

You can visit your website on your host machine in a browser at [VPN INTERNAL IP]:[VPN FORWADED PORT]. For me, using the internal IP is required to view the website on my host machine.

To view the website on other machines, you can use [VPN EXTERNAL IP]:[VPN FORWARDED PORT]. The only thing you need to change is the IP address.

I hope this works for you and you are inspired to selfhost and take back power from those who stole it from us.

[–] humanoidchaos@lemmy.cif.su 1 points 1 day ago* (last edited 1 day 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.

[–] humanoidchaos@lemmy.cif.su 1 points 1 day ago (3 children)

Thanks. Now I'm getting validating 2009scape-master/docker-compose.yml: services.healthcheck additional properties 'timeout', 'interval', 'retries', 'test', 'start_period' not allowed when I run docker-compose up.

I'm using the repository at https://gitlab.com/2009scape/2009scape

[–] humanoidchaos@lemmy.cif.su 0 points 1 day ago* (last edited 1 day ago) (1 children)

Just so we're clear, you think news outlets don't use the word "migrant" in place of "immigrant" when the subject(s) is question are known to be immigrants or trying to immigrate?

A simple yes or no will suffice.

[–] humanoidchaos@lemmy.cif.su -1 points 1 day ago (1 children)

So... what was the problem? How did it get "insane"?

Is it because nobody else "big" joined them? Is it because, and hear me out, they decide it was no longer worth the money?

[–] humanoidchaos@lemmy.cif.su -3 points 1 day ago* (last edited 1 day ago) (1 children)

Tired of arguing with you people.

That doesn't mean he's correct or has a point, which he doesn't.

But hey man, you do you. Let people waste your time.

 

I’m trying to add my instance to Fediseer at https://gui.fediseer.com/auth/claim-instance so it can federate.

When I try to send the message, I get an error saying: There was an api error: API Key PM failed

I’m not really sure how to diagnose something like this, but I tried sudo docker logs [ID of nginx container] and one of the entries says "POST /inbox HTTP/1.1" 400 86 "-" "Fediseer/0.25.1" after I try sending the message.

I’m assuming this has something to do with it, but I’m not sure if that’s true or how to fix it even if it is.

Any help would be greatly appreciated.

view more: next ›