BlueEther

at my age you want me to remember what I did 5 months ago? I can hardly remember yesterday…

I think it was something like:

• ~2kg manuka honey (I have a ‘free’ supply of manuka, from cleaning out filters between batches, just have to filter all the bits out once diluted down)
• tablespoon-ish of Motueka hops (the compressed pellets)
• water to ~4.5L

This had a really slow finish, so bottled with some sweetness and still the last bit of ferment left, maybe dont try this if you want to avoid bottle bombs. This did end with only a light sparkle and not a full carbonation

I just use straight up tap water right out of the tap here, although I do have access to filtered rain water (that I know is not as ‘clean’ as town supply water)

If the yeast is happy as you are doing it now then I’d say all is good.

Hi and welcome to the rich world of mead brewing.

As I type this I have a dry hopped manuka sparkling mead in my hand.

1. I use Fermaid AT and just dump it in

2. anything that has a lot of CO~2~ in it will degas if you give it lots of nucleation points (ie dump a pile of powder in it) degassing first will help with that

3. I sanatise too much (mostly just the brewing vessel, airlocks etc) Most other stuff (stainless steel) is rinsed under tap water. Honey is already full of yeasts* and stuff, so unless you are doing metabisulfite 24h before pitching yeast there will always be stuff in there already

• One thing to start to try as you go down the road is wild ferments - you can get some very interesting flavours, some good and others not so good

thanks you and @Irdial@lemmy.ml LM Studio was the tool I think I was looking for

I have AdGuard Home running on OPNSense as a local DNS with a wild card for for the ‘local domain’ pointing to Caddy

in Caddy I have this section:

*.<domain>.net {
#header X-Frame-Options "SAMEORIGIN"
        tls internal
        encode gzip
        import sec-headers
        @sub1 host pve.<domain>.net
        @sub2 host kasm.<domain>.net
       ...
       handle @sub1 {
                import sec-headers
                reverse_proxy * https://10.1.1.11:8006/ {
                        transport http {
                                tls_insecure_skip_verify
                        }
                #       header_up Host {host}
                       header_up X-Real-IP {remote}
                       header_up X-Forwarded-For {remote}
                       header_up X-Forwarded-Port {server_port}
                       header_up X-Forwarded-Proto {scheme}
                }
        }
        handle @sub2 {
                import sec-headers
                reverse_proxy  https://10.1.1.119/ {
                        transport http {
                                tls_insecure_skip_verify
                        }
                #       header_up Host {host}
                       header_up X-Real-IP {remote}
                       header_up X-Forwarded-For {remote}
                       header_up X-Forwarded-Port {server_port}
                       header_up X-Forwarded-Proto {scheme}
                }
        }
...

Back up the server then work through:

Just follow the guide iocaine.madhouse-project.org/…/getting-started/ Bind the iocaine service to 0.0.0.0:42069

cat /opt/iocaine/etc/iocaine/config.d/00-server.txt.kdl 
http-server default {
  bind "0.0.0.0:42069"
  use handler-from=default
}

expose interface to Docker (make sure not to expose it to the world).

sudo iptables -I INPUT 4 \
  -s 172.18.0.0/16 \
  -d 172.18.0.1 \
  -p tcp --dport 42069 \
  -j ACCEPT

add the interface to the proxy service in a custom/docker-compose.yml.template

proxy:
    {{COMPOSE_CADDY_IMAGE}}
    env_file:
      - ./caddy.env
      - {{ CADDY_EXTRA_ENV }}
    volumes:
      - ./caddy/Caddyfile:/etc/caddy/Caddyfile:ro
      - caddy_data:/data
      - caddy_config:/config
    extra_hosts:
      - "host.docker.internal:172.18.0.1"
...

add iocaine to caddy in a custom/Caddyfile.template

{$LEMMY_HOSTNAME} {
        import caddy-common

        ######################################
        ########## log files        ##########
        log cn_blocked {
                output file /data/cn-blocked.log
                format json
                no_hostname
        }

        ########## iocaine  code ##########
        @read method GET HEAD
                reverse_proxy @read host.docker.internal:42069 {
                @fallback status 421
                handle_response @fallback
        }
...

rebuild all the docler images (at least the caddy one ./deploy.sh -f) and test

I think that should work

Well done on getting it up and running, federation seems to be working moplemmy.fyi/instances

You shouldn’t have to put instances in the Allowed Instances, just use blocked list for stuff you dont want to see

Yes email is a pain in the arse. More so if you are having to deal with dynamic IPs

Now just wait for the scrapers to turn up. Both Dave (lemmy.nz) and I are getting well in excess of 500k requests from content scrapers per day atm and they are tyring to pull in whole comment trees and walk through all posters.

Have a look at Iocaine to help tarpit some of them if you dont want to route through something like cloudflare.

And yes - I’m running DSM (Arc Loader) in a VM with PCIe passthrough for the NAS. It’s a bit overkill, but I wanted proper storage virtualization with direct hardware access.

Whats this like, I’m running TrueNAS (the BSD version) with PCIe pass-through for my HBA and a couple of SATA ports.

• No where on the network page does it say to use app.plex.tv when you have a custom domain with ssl certs
• I wanted to cast to a dumb TV with a chromecast, the macos app doesn’t seem to support that
• if it was my network it would still not work, but it is again with no changes to the local network or to plex settings
• Plex is seeing a local IP in the logs when accessed via a FQDN

how is using a FQDN user error when the logs show the access is from a 10.1.1.x address?

I looked back at jellyfin’s history. I have had it installed for over 3 years, just not transitioned to uisinf it as up until last night plex had worked just fine (even with remote access)

I have always connected via a FQDN, for some reason last night it decided to shit it’s self. Resolved by accessing via local IP, then the FQDN worked again

I have always connected via a FQDN, for some reason last night it decided to shit it’s self. Resolved by accessing via local IP, then the FQDN worked again

because like 10 years of use, maybe more?

the thing is I always use the network name. Once I used the IP I couls go back to using plex.<mylastname>.TLD

well everythig has been working fine for years as is, and still works fine on firefox (I wanted to cast to chromecast tonight, it worked fine 2 days ago)

I did try and preempt that in my comment - but it’s hard to switch from plex when there are 5 other people with everything all configured and history etc