Many games have launchers which can be skipped by entering a command to the launch properties in Steam. Check the games info page in ProtonDB

That’s why I always:

• cd .cache
• ls
• rm -r *

Anyone else get the urge to pull the hat down?

You can’t trick me, I know a bullet hell when I see one.

OK!

SAY IT WITH ME NOW!

WHEN I SAY “BARBARA” YOU SAY “STREISAND”!

READY?!

" BARBARA "

Because.

Would like an easy way to remember.

• mnt = mount
• opt = optional ?
• etc = etcetera ?
• proc = process ?
• srv = server ?
• var = variable ?

I’ll give this a go soon

Appreciate all the help this far.

I think this issue is either application or OS related.

I’ve been wanting to wipe my server and start fresh for a while to work with NixOS.

As a beginner, I’m sure I’ve changed some obscure setting, somewhere, which has just broken everything. I don’t think it’s worth it to diagnose.

But definitely learned a lot in the process of following your advice, so thanks heaps :)

Thanks again for trying to help me, it’s really appreciated, I’m tearing my hair out.

Externally, I can access all services via their ports, except SWAG (port 80 and 443).

Internally, (from my PC to my server on the same local network) I can access:

• jellyfin.<user>.duckdns.org (secure)
• <user>.duckdns.org:8096 (not secure)
• <user>.duckdns.org:80 - routes to the SWAG homepage at https://<user>.duckdns.org (secure)
• <user>.duckdns.org:443 - as above

#.

If I try to use curl on <user>.duckdns.org I get:

• Host <user>.duckdns.org:80 was resolved.
• IPv6: <ipv6 address>
• IPv4: <ipv4 address>
• Trying: <ipv4 address>
• Trying: <ipv6 address>
• Immediate connect fail for <ipv6 address> Network is unreachable
• Connect to <ipv4 address> port 80 from <external ipv4> port 40264 failed: Connection timed out
• Failed to connect to <user>.duckdns.org port 80 after 31235 ms: couldn’t connect to server
• Closing connection

Thanks, this put me on the right track (I think).

I still can’t determine what is wrong exactly.

I can access my other services with <user>.duckdns.org:<port>

But for some reason ports 80 and 443 are exclusively failing to connect, despite all port forwarding rules on my router being identical, and my server’s firewall permitting access to those ports.

Could it be some kind of security on my router or server is intercepting the connection?

Oh no, you’re going to make me be that guy lol.

Ricing comes from “rice cooker”, meaning a Japanese car. The term is so far removed from any racial implications now, that some people say RICE means “Race Inspired Cosmetic Enhancements”, though it’s just an excuse where one need not exist.

I regularly see people brigade for others to stop saying it, even though the word now exists on its own. People treat it like it’s comparable to something like the Washington “Redskins”, it isn’t.

“Ricing”

Uh oh, you said the forbidden word. Won’t be long until everyone in this thread is “informed”.

What you’re referring to as GNUI, is in fact GNUI/Linux or as I’ve recently taken to calling it, GNUI plus Linux.

Did you just say GUI?

More like ewwwie.

Me, a sick fuck, who likes a quick fuck:

/etc/moron-syntax/I\ write\ like\ a\ gay\ fish\ \(\Kanye\)\

That’s why camelcase starts with a lower letter. If you’re using a good terminal+shell setup then it’ll be irrelevant most of the time.

I’m more worried about Google’s income. How can they afford to spy on me if they aren’t being paid far out the ass to host what will soon be security theatre.

How old?