• 3 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: September 13th, 2023

help-circle








  • Do you actually know those people IRL? People on the fence? I haven’t talked to anyone who hasn’t already had their vote decided. The political climate has been the most divisive in my lifetime, to the point where the people I’ve spoken with IRL are either dug in with Trump or dug in against Trump. This scene doesn’t change Trumps degressive views or awful policies. It doesn’t change Trump from being a Felon or suspected pedophile.

    If there are swing voters it’s likely a really small number. At the end of the day the Democrats are dug in on Not Trump, and they have the numbers. They showed up for the last election, and the divisive politics have kept it in their peripheral since. RvW was huge, 2025 has been getting traction. There ain’t many left that don’t have their political compass set.




  • …you’ve got apathetic D voters who really don’t want Biden to be president.

    Let’s be real, nobody wants Biden to run again, on either side. That being said, every Democrat knows what’s at stake - and that’s Donald fucking Trump. This situation doesn’t change who DT is, his viewpoints, or his policies. The actual people, the actual voters realize that DT is just a way worse situation.

    It’s not about changing voters’ votes - our elections are never about that - t’s about the number of people who cast a vote.

    This nothingburger of a scene isn’t going to stop some Democrat from voting. At the end of the day, there are more Blue than Red and the Dems are entrenched in not having DT in office. I don’t even live in a big city, a red county even, and everyone I’ve talked to in person understands the stakes.

    Yesterday’s event changes that.

    Why would yesterdays events change your viewpoints on Turmp? How does that change his awful policies and degressive viewpoints? How does that change him being an actual Felon and suspected pedophile?








  • ProtecyaTec@lemmy.worldOPtoSelfhosted@lemmy.worldHTTPS with FreeDNS
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 months ago

    I don’t know if this will help anyone but damn is the documentation on how to do this kind of thing scarce so here I am. I was quite a struggle both learning all this and implementing it but it’s been fun overall.

    FreeDNS doesn’t seem to have a way to add any kind of SSL Certs as far as I can tell. Not that I needed to, but when I tried explaining my situation to the hosting provider they suggested that the cert needed to be on the DDNS server.

    I also couldn’t get the Asustor Reverse Proxy to work either. Many of the tutorials and user suggestions i ran across suggested that this is the way to get SSL but when I tried to implement it I kept landing at my portal login and nothing was getting proxy’d. The netstat command was showing that whatever the reverse proxy port needed was not open - I also ran across this in a 2020+ thread on Asustor.

    Right now I’ll also need to manually update the certs and go through this process again in 3 months time. There might be a way to automate this process but it’s a lot of steps that I’m not sure can be automated in this seeming (to me) flawed setup. In any case, it’s been challenging but fun and I think in the next 6 months I’ll upgrade out of Asustor and into a bigger server with a core Linux setup. I know nothing about Linux :)


  • ProtecyaTec@lemmy.worldOPtoSelfhosted@lemmy.worldHTTPS with FreeDNS
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 months ago

    I do appreciate everyone’s suggestions and help. Here’s what I ended up doing.

    FreeDNS via freedns.afraid.org as a DDNS Subdomain

    Domain + Subdomain via hosting provider

    Hosted Subdomain CNAME to the DDNS Subdomain

    Setup DDNS using Asustor > Settings > Manual Connect and setting up a FreeDNS account and input the info it needed. Last DDNS update keeps coming back as Failure but FreeDNS keeps updating my IP so it seems to work, but for whatever reason Asustor doesn’t think it’s working.

    Used openssl + certbot CLI tools to generate a certificate that covers all 3 cases: Hosted Subdomain, Hosted Domain, DDNS Subdomain. Looks like this:

    certbot certonly --key-type rsa --rsa-key-size 2048 --manual --preferred-challenges dns -d hosteddomain.example -d subdomain.hosteddomain.example -d ddns.domain.example
    

    This will set up verification codes that you can create TXT records for on the Hosted Domain and the DDNS Domain. I had to contact FreeDNS to get access to add text records with underscores but they were cool and quick to reply. They look like this:

    _acme-challenge.hosteddomain.example
    8suZTccF9ZpB0fnBr9mgEEXTcX7cqSkDXiBzucTcOfw
    

    Once the certificates are in place I uploaded them to my Hosted Domain and verified that my Hosted Domain was showing the SSL certificate / lock at HTTPS.

    Next I logged into my Asustor and under Settings > Certificate Manager I added my SSL Certificates and assigned it as the primary certificate for the NAS.

    Finally, I needed to enable SSL on my Jellyfin, which required a PFX file.

    openssl pkcs12 --export -out "Z:\Path\To\PFXOutput\jellyfin.pfx" -inkey "Z:\Path\To\Cert\jellyfin.key" -in "Z:\Path\To\Cert\jellyfin.crt"
    

    Under Jellyfin > Dashboard > Networking I enable HTTPS, Require HTTPS, give it the path to the PFX file and the PFX password, and Allow remote connections to the server. I disabled port forwarding from Jellyfin and had to jump into my router to remove the UPnP records it had previously added. All port numbers are default to Jellyfin and no URLs in the Server Address Settings.

    Important to take note of the Jellyfin ports here for both HTTP and HTTPS requests. Important note to restart Jellyfin after this takes effect. Asustor has an App Central where under Installed Apps you can just turn it off and back on again.

    Finally, I added Port Forwarding to my router so that the 443 looks for the Jellyfin HTTPS port and 80 looks for the Jellyfin HTTP port at my NAS IP.

    Now I can access HTTPS subdomain.domain.example and land at my Dockered Jellyfin app.