Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Pretty much nobody can help you with the information you provided there.
Minimum required is going to be a 'ufw status' output. The whole output, not an edited partial output.
So you want to block port 22? Yet the rule you added allows access, or am I misunderstanding?
You probably need to be DENY instead of ALLOW if that's what you're wanting to accomplish.
This! You have it set to “Allow”, so it’s allowing it. You need to set it to Deny.
I understand it
Is this a troll post or are you really struggling?
really struggling
Is this a public facing server? If it isn't the online port port scanners will not work as they are scanning your public IP. Also they are unreliable in general. Best tool for the job is nmap. It has a ton of config options so you will need to do some reading. (Definitely worth the learn)
Do you have something listening on port 52038 that will respond to a port scan? If not it will report as closed.
It's my port for wireguard and here what I can't understand: when I blocking port for this wireguard service I still can use wireguard even if ufw deny it.
Wireguard appears as closed unless it receives the proper packet.
that's what I looked for
Is wireguard incoming or outgoing from the machine you're trying to block it on?
outgoing, I guess. I mean, it's on my vps which I want to use for vpn
Make sure you're creating a block rule specifically on outgoing in that case.
when I just use
ufw allow [port]command it'll not work?Outgoing should already allow everything, so no need to specifically allow it.
That's a website tool checking? It's almost certainly only going to check TCP, since most of them don't do anything with UDP because it's... more complicated.
You may need to find an alternate way to do that, something like iperf or netcat (nc -u ip port)
nmap works great for this
traceroute might also be usable vith the -p switch I guess?