Search

cross-posted from: https://lemmy.ml/post/15121280

> preferably with a web console (not required)

Edit: I went with this as a solution for now: https://github.com/Ashfaaq18/OpenNetMeter

Does someone know how to get listed? I configured the admin settings to be a public instance AFAIK...

https://lemmyverse.net/?query=lemmy.tellyou.social

I've been wanting to set up a small game server on my home network for myself and a few friends lately. Nothing I haven't done before - except the part where I open it up to the internet for people outside of my home network to play on.

So I tried setting up a small web server to test out the port forwarding functionality of my router. Darkhttpd, running on a spare Raspberry Pi, works fine on the local network. After digging through the web interface, I find out that using IPv4 isn't an option because of how my ISP tunnels network traffic (sth sth Dual-Stack Lite)—fine by me, in 2024 we should be using IPv6 anyway. So I go and open up port 80 in my router's web interface.

This is where the problem begins. Everything looks fine, but I don't have ready access to a network outside of my own to check if the port is actually accessible from the internet. An online IPv6 open port checker I found tells me the ports are visible and that my ISP isn't blocking anything. Trying to bind a domain that I had lying around to my IP address, however, has resulted in failure.

I have no idea how to debug this. I'm pretty sure there's some issue on the DNS Server end, but I can't even tell if the rest of what I'm trying to do is working. And if it is, I have no idea of how to go about fixing the DNS thing.

Update: I got a friend to test it, and the web page is accessible from the internet. Problem lies with the DNS server

Update 2: After contacting my friend again for a sanity check, it seems that the DNS server works fine and my test website can indeed be reached through my domain—it's just that I can't reach it.

Update 3: After poking at various DNS servers, it appears that the Mullvad DNS servers which I use don't regularly update their records. I've now switched to Cloudflare. My router similarly implements some caching solution that, after much tinkering, I was unable to flush. For the time being I've just decided to fuck doing this properly and directly edit my /etc/resolv.conf with the Cloudflare DNS servers. If I ever manage to get this working properly, I will add a final update, but for the time being, I will consider it solved.

Hello all. I'm trying to change the SSH port on an Oracle VM, but I'm getting nowhere and I don't know where to solve the issue.

I have changed the SSH port:

edit /etc/ssh/sshd_config

Entered the port info:

Port 5522

I restarted the service: sudo systemctl restart ssh

And made sure that the port is open: ss -an | grep 5522 tcp LISTEN 0 128 0.0.0.0:5522 0.0.0.0:* tcp LISTEN 0 128 [::]:5522 [::]:*

***

I also allow incoming traffic to 5522: sudo ufw allow 5522/tcp comment 'Open port ssh tcp port 5522'

AND just to make sure, I allow 'routed': sudo ufw default allow FORWARD

And make sure the FW config is valid: ``` sudo ufw status verbose Status: active Logging: on (medium) Default: deny (incoming), allow (outgoing), allow (routed) New profiles: skip

To Action From -- ------ ---- 22/tcp ALLOW IN Anywhere # Open port ssh tcp port 22 5522/tcp ALLOW IN Anywhere 22/tcp (v6) ALLOW IN Anywhere (v6) # Open port ssh tcp port 22 5522/tcp (v6) ALLOW IN Anywhere (v6) # Open real ssh tcp port 22 ```

Yet, I cannot connect to this server. Trying to ssh -vvvv -p 5522 [ip-adress] yields this:

OpenSSH_9.0p1 Ubuntu-1ubuntu8.4, OpenSSL 3.0.8 7 Feb 2023 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolve_canonicalize: hostname 129.x.x.5 is address debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/x/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/x/.ssh/known_hosts2' debug3: ssh_connect_direct: entering debug1: Connecting to 129.x.x.5 [129.x.x.5] port 5522. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: connect to address 129.x.x.5 port 5522: No route to host ssh: connect to host 129.x.x.5 port 5522: No route to host

I can connect just fine when the port is at 22, but as soon as I change it to 5522, i get the 'no route to host' error.

I've made sure I have rules on Oracle cloud that allows ingress and egress traffic to 0.0.0.0/0 on all protocols, no matter the destination / source.

What am I doing wrong? It feels that this problem is host (server) based rather client based, since I'm getting a routing error. Do I need to configure the routing for that port specifically, and if so how?

PS: Also, connecting to localhost:5522 from the server itself works fine. So the problem is not in the configuration, but likely network related.

---

EDIT: This issue is solved, solution written on this post: https://lemmy.ml/comment/2787074

I don't have any other servers that i could run the whole time so it should just be based on one single device,

I did it with Lemmy Easy Deploy

I have a Raspberry Pi with a 2TB SSD on which I store all of my media. That media sits in a directory that is capable of being mounted on other computers via NFS.

I have that directory mounted on another computer via NFS in /mnt. I am able to create directories, create files, move files there, and they show up instantaneously on the Raspberry Pi (I do this without sudo because I gave my user write permissions via chown).

However, when I attempt to download a torrent via Transmission and have it automatically save to the NFS-mounted share, it does so for a few seconds, then gives me one of the two following errors:

Error: Permission denied (/mnt/....)

or

Error: Read-only filesystem (/mnt/....)

My Transmission Daemon user is set up to be my normal user.

Anybody have any ideas? I followed these three tutorials to set it all up:

• https://pimylifeup.com/raspberry-pi-transmission/
• https://pimylifeup.com/raspberry-pi-nfs/
• https://pimylifeup.com/raspberry-pi-nfs-client/

Thank you in advance for any help you can provide.

I have Jellyfin on my Raspberry Pi and I usually access it via my local network or via SSH tunneling when I'm outside of my local network, but I want to be able to just access it via https outside of my local network.

I am following the instructions on Jellyfin's Networking page here: https://jellyfin.org/docs/general/networking/

On the part where I input this command

openssl pkcs12 -export -out jellyfin.pfx -inkey privkey.pem -in /usr/local/etc/letsencrypt/live/domain.org/cert.pem -passout pass:

I get this error

Can't open /usr/local/etc/letsencrypt/live/domain.org/cert.pem for reading, No such file or directory

Any idea what I'm doing wrong?

Got it solved! For future people reading this, the solution is here: https://github.com/jellyfin/jellyfin/issues/6697#issuecomment-1086973795

Jellyfin's Networking guide is all wrong.

Okay, so I followed some guides starting with this one that uses CLI but then ended up roughly-following this Docker guide. I'm running Ubuntu so I had to figure some things myself.

My SSL settings are set to encryption mode full, my tunnel settings are as follows\ ! !

My Owncast server is set up to 30050 and I can even connect fine through external IP, but Cloudflare's not cooperating. When I connect via my hostname, I get a 502 error, and on the server side I get the following errors: ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:30050: connect: connection refused" cfRay=7d6fe3954bcd5419-YYZ event=1 ingressRule=0 originService=http://127.0.0.1:30050/ ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:30050: connect: connection refused" connIndex=1 dest=https://live.ramram.ink/favicon.ico event=0 ip=198.41.192.7 type=http I also confirmed that on the local machine, running curl 127.0.0.1:30050 works fine.

Hi guys, would be happy to receive some input on my current problem. I spun up my own Lemmy instance yesterday using the ansible playbook on newly set up VPS with it's own IPv4. Since I also had an unused domain I choose to use it exclusively for Lemmy. I therefore set the domain in the hosts file to exactly that one. I created the follwing DNS entries in Cloudflare for it:

• A Record with name www pointing towards the ip
• A CName pointing the domain without subdomain towards the www.subdomain.de thing

Both without a activating their proxies. As soon as I'm activating their proxies my instances becomes unreachable and if I'm calling www.my-domain.de I'm seeing an Nginx error page. Is there a smart way anyone of you knows how I could setup my dns records in a way that I'm able to use Cloudflare proxies to kinda encapsulate my vps a bit more?

EDIT: I got it solved, first on, I was most probably an idiot when setting the SSL settings. I could be possible that I changed them for the wrong domain. So in the end I did two things. First on I changed the CNAME thing into another A record pointing directly towards the server ip. I suspect this was not the root cause. Because after changing the DNS settings I discovered that again the SSL settings were set to Flexible this is basically a setting where Cloudflare assumes you are somehow unable to get your own SSL certificate on your server and therefore only the traffic between the users browser and them is encrypted but the traffic towards your server is not. That was most probably the main reason since this should cause an infinite forwarding of Cloudflare trying http but my server was redirecting them to https (for more info see here). I set it to Full (strict) meaning now all the traffic is encrypted using my certificate.

After both changes it works now, and when pinging the url some random Cloudflare IP shows up and "my" ip is hidden.

Old DNS settings: !Old DNS settings

New DNS settings: !New DNS settings

EDIT 1: Changed the title from xyz (SOLVED) to [SOLVED] xyz

Edit: Solved! See solution in comments

I’ve setup a self hosted lemmy docker and it works when accessing directly on the same subnet.

I don’t have ports opened in my firewall and my ISP don’t offer static IP so I rely on Clouflare tunnel as an alternative.

I’m able to load the front page, but can’t sign in. I don’t cache JavaScript through Cliudflare so I believe it’s relating to Websockets, but curious if anyone else has been able to get this working?