wgstarks

Thanks. I guess the part of the announcement about it having a new home made me think it was moving.

If CA is moving away from the Unraid tab to a new website what’s the install process going to look like? I don’t see any install buttons on the new website.

You can use the openssh docker and setup your users and access there.

Nevermind. I got it. Had just copied the server address from my browser and pasted it in. Once I edited it to remove https//: and /Main it worked.

Lost connection to server and cannot reconnect. Current settings- When I try to connect I get a network error Could not parse data to JSON format.

I get an execution error when trying to stop this docker. Unraid 7.3.1. docker run -d --name='HDHomeRun-Signal-Web' --net='bridge' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="BrunnhildeTwo" -e HOST_CONTAINERNAME="HDHomeRun-Signal-Web" -e 'PORT'='3000' -e 'HDHOMERUN_DEVICES'='' -e 'HDHOMERUN_DISABLE_DISCOVERY'='false' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:3000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/petelombardo/unraid-templates/main/icons/hdhomerun-signal-web.png' -p '3000:3000/tcp' 'petelombardo/hdhomerun-signal-web' 41044ee444d0009dc0f77d981e69c78c68cb6c5f38f51b53b2762236351a2370 The command finished successfully

Attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

Done https://product.unraid.net/p/7-3-1-management-access-help-shows-invalid-pfsense-rebind-config?b=unraid-os-bugs

That’s not supposed to be an issue anymore according to LT but I recently had a bunch of unexplained (nothing in the logs) system freezes that totally disappeared after changing MACVLAN to IPVLAN so I would have to agree with you. It’s possible that whatever is causing this issue may be hardware dependent I suppose.

Not sure if that matters. Saw a bunch of examples that had either one. I used singles though.

Actually the instructions may have said separate lines. Not sure about the exact wording but my assumption was that if each setting should be on a separate line then settings that took up two lines wouldn’t work. Changing the setting so that it was all on one line fixed the failed dns query. The full discussion on the pfsense forum is here if anyone is interested. It really illustrates my lack of knowledge when dns is involved.😁

A little more info from the pfsense forums. The settings page in pfsense states that settings should be separated by a line break. The unbound docs state that only a whitespace is needed but recommend using line breaks and indentation for visual clarity so the currently suggestion in the help menu should work but doesn’t.

Actually got this fixed too. It seems that the pfsense setting recommended in the Unraid help menu in management access settings isn’t formatted properly. The help menu shows adding this setting in pfsense- server: private-domain: “myunraid.net” What actually worked was this- server: private-domain: ‘myunraid.net’ No line breaks.

Actually got it fixed with help from Google. Looks like it was a corrupted certificate bundle. Deleted /boot/config/ssl/certs/certificate_bundle.pem and then re-provisioned in settings>management access. Everything is working now.

I have avoided making any changes to this server other than the docker network type for more than a week and haven't had anymore recurrances of the freezes. Changing macvlan to ipvlan seems to have fixed the problem.