Ah. Yeah. I think then you’ll want to look into cloudflare tunnels. I believe that should get you through the cgnt and deal with the dynamic IP ll in one go.

You can deal with the non-static IP by using duckdns.org

I’ve got a raspberry pi 4 (8GB) running Kodi (via osmc) hooked up to our tv. The tv itself is a Roku tv that isn’t allowed to connect to the internet.

I’ve also got a pc that used to be my streaming/video editing rig back when I used to make videos, but I repurposed it as my server, and it runs Jellyfin, along with a host of other apps/services for me and my family.

The pc is older, but as a server it works great. Biggest drawback is power consumption, it’s not nearly as efficient as a mini pc with a n100 or something similar, but for my purposes it works great.

Awesome! Just joined the test flight. Love the app icon.

Okay, please point me to the blog posts that helped you with collabora/onlyoffice. Thanks have NEVER been able to get that to work with my nextcloud (currently using the Docker AIO).

There’s also Plappa for iOS on the App Store. Great alternative to the abs beta app.

Just posted my setup

So, this took way longer than I thought it would, mostly because I needed the time to sit down and actually type this up.

Full credit, I followed the instructions in this video from Wolfgang’s Channel

Prerequisites (this is based on my setup, the api key requirement will vary based on your domain registrar/service):

• Docker & Docker Compose
• NGINX Proxy Manager running via Docker
• A registered domain to use for your lan
• An API key from your domain registrar/service

I’m running NGINX Proxy Manager, using this docker-compose.yml, which I got straight from the NGINX Proxy manager website.

version: '3.8'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

I’ve got my domain managed by Cloudflare (yes, I know they’re evil, what company isn’t?), so these instructions will show setup using that, but NGINX Proxy Manager supports a whole bunch of domain services for the HTTP-01 challenge.

With all prerequisites in place, here are the steps:

• Log in to your NGINX Proxy Mananger (you can access the service and login at port 81 of the machine hosting it)
• In the top menu, click the SSL Certificates tab
• Click the Add SSL Certificate button
• Choose Let’s Encrypt for the certificate type
• In the Add Let’s Encrypt Certificate dialog, input the following
  • Domain Names: Input the domain root, as well as a wildcard subdomain. You’re entering both domains into the same field. After entering each domain, press the enter/return key on your keyboard to confirm the domain. For example, if you domain is abcde.com, input:
    • abcde.com *.abcde.com
• Email Address for Let’s Encrypt: Any valid email address you’d like to use
• Toggle the Use a DNS Challenge option on (when you toggle this on, a new set of options will appear)
  • DNS Provider: Choose yours. I chose Cloudflare
  • Credentials File Content: Delete the prepopulated dummy api key and paste in your actual api key
• Propagation Seconds: I put in 120 to give it two minutes. You can try leaving it blank, but if the DNS records haven’t propagated, you may get an error (I did when I tried leaving it blank during setup).
• Toggle on the I Agree to the Let’s Encrypt Terms of Service option - Click Save

Once you get a success message, you can start creating proxies with NGINX Proxy Manager for your internal domain. To do that you will need the ip address and port you are forwarding the domain to for your lan service. If you are using Docker containers, you’ll need the Docker ip, which you can get from the command line with:

ip addr show | grep docker0

You should get an ip address like 172.17.0.1

Otherwise you’ll just need the ip address of the machine you’re running the service on.

To set up a proxy redirect:

• In NGINX Proxy Manager click the Hosts tab/button and then choose Proxy Hosts.
• Towards the upper right click the Add Proxy Host button
• In the New Proxy Host dialog box, input the following:
  • Domain Names: input the domain address (subdomain or tld) you wish to use for the service. For example. homepage.abcde.com, then press enter to confirm the domain
  • Scheme: leave set to http
  • Forward Hostname/IP: Input either the host machine ip, or the docker ip
  • Forward Port: Input the appropriate port for the service
  • Cache Assets: Toggle on
  • Block Common Exploits: Toggle on
  • Websockets Support: Toggle on if the service needs websockets
  • Click the SSL tab of the New Proxy Host dialog box to set up the ssl certificate
  • In the SSL tab, input the following:
    • Click the None under SSL Certificate and select your local domain + wildcard subdomain certificate
    • Toggle on the Force SSL, HTTP/2 Support, HSTS Enabled, and HSTS Subdomains options
    • Click Save

Once the save is complete you should be able to input the new domain for you lan services and get a secure connection.*

*Bear in mind some services require you to specify a valid domain for the service within the config/settings. Double check any services you may be running for this if you plan to use a reverse proxy with them.

Haven’t forgotten. Just haven’t had time. I’ll get a write up ASAP

That’s totally fair. Wordpress can accomplish what you want, but also can be a giant nightmare. I ran a membership based Wordpress site for around a decade (self hosted and maintained), and it was mostly okay, but also many times a giant headache. I fully understand wanting to avoid Wordpress.

I can. I’ll report back with details tomorrow when I have time.

This is exactly how I have mine set up and I really like it.

I’ve got an internal and external domain with a wildcard cert so if it’s a local only service I can easily create a newservice.localurl.com, and if it’s external I can just as easily set up newservice.externalurl.com

I’m not entirely sure what you mean by userbase, but based on your description it sounds like you could set up a Wordpress docker container with some plugins to handle what you want and then use the Wordpress api for the calls. If you’re looking for like a paid membership situation for the site, there are free and pay plugins that can accomplish the payments and subscription integrations.

I’m currently using Baserow, and so far it suits my needs well enough. I’m not a very demanding user, but part of what I love is how nicely Baserow documents the api. It made it very easy for me to implement some automations I wanted to use to record data.

Edit: fix stupid autocorrect errors

Oh dang. How fun. I never even considered thematically making my machines! Mine are super mundane.

• machine - main server
• osmc - Kodi media box for tv
• kmac - old iMac running kde neon
• tunnelpi - raspberry pi 4 wireguard tunnel access point
• mini- Mac mini my wife uses for day to day use.

Now I’m going to have to find a theme and start renaming machines! I might go with Magic the Gathering as my theme.

Edit: formatting, and added MtG as potential theme

Edit 2: fixed stupid autocorrect error (theatrically to thematically)

+1 for mealie. Been running it for maybe six months now and it’s great.

Also been thinking about doing something like this. Would love to hear about your experience deploying it.

Nice!!! I’ve been using the audiobookshelf beta for my server, but I like the look of Plappa. Gonna give it a spin!

Absolutely. I’ve burned a number of things to the ground as I figure out what tf I’m doing. I’ve learned a lot doing it too!

Also switched from homarr to homepage and have been happy with homepage.