• 1 Post
  • 59 Comments
Joined 10 months ago
cake
Cake day: December 26th, 2023

help-circle












  • 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 :)


  • Zozano@lemy.lolOPtohomelab@lemmy.ml[Help] Can't get my URL to work.
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 months ago

    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

  • Zozano@lemy.lolOPtohomelab@lemmy.ml[Help] Can't get my URL to work.
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 months ago

    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?


  • Zozano@lemy.loltoLinux@lemmy.mlSelect Audio Output Via Command Line
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    2 months ago

    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.