slashmach1

Members
  • Posts

    8
  • Joined

  • Last visited

slashmach1's Achievements

Noob

Noob (1/14)

4

Reputation

  1. Just to preface this so you are aware: This seems a kernel bug, not sure if anything can be done on your end about it. My server motherboard is an MSI MORTAR 660 MATX intel board. Noticed when server booted the cpu and system fans would run but would not throttle or respond to temperature changes. This board at least seems to use a PWM chipset that isnt detected or loaded automatically by Unraids kernel on boot. Manually loading the module from cmdline/shell with modprobe nct6683 allows it to be detected and once that step is done the fans throttle properly by temperature. Just uploaded a hardware profile from the server
  2. thats the trick though, myserver plugin was not installed in my case and had unregistered the hostname for letsencrypt ssl a long time ago. IP login even with broken SSL had worked up until i updated to 6.10 stable from 6.9.2
  3. it may be a little more complicated then that. poking it some more and it looks like it is going off of the full hostname if you had ever previously registered the myserver plugin for ssl or to a custom hostname. I had to use hostname.domainname.net to get the hostfile to work correctly.
  4. in windows the hostfile is at C:\windows\system32\drivers\etc\hosts hostname anonymized below: 192.168.10.254 myhostnamehere just submitted bug report to describe my findings
  5. I have found that this may be due to the new additions involving Letsencrypt. My system would not connect by IP. Added a hostfile entry that points to it and BOOM i was able to connect.
  6. I have found that this may be due to the new additions involving Letsencrypt. My system would not connect by IP. If you know your system hostname add a hostfile entry that points to it and BOOM i was able to connect.
  7. The enclosed script is my own creation for using a Dockerhub Google Cloud SDK image in order to run API commands for DNS updates. This script starts a Docker container, runs the command, and discards it. The persistent storage is in the appdata directory and should be mounted each time a new project is initialized or command is run. This is intended to be run via the User Scripts plugin. Simply tweak the script to your liking and fill in the variables at the top. Please do not ask for support regarding the Google API commands as I am no expert on all the details of what that entails, its simply provided as a starting point for those looking to run the GCloud SDK on Unraid without dedicating a VM to the task. Before the script is run you will need to run the gcloud auth login and gcloud workspace commands with the persistent storage attached. Directly from command line that would look something like this: docker run --rm -e CLOUDSDK_CORE_PROJECT=$PROJECT_NAME -v /mnt/user/appdata/gcloud:/root/.config/gcloud google/cloud-sdk gcloud auth login I use the LinuxServer.io Letsencrypt (SWAG) container with Google DNS authentication for a wildcard web certificate. There does not seem to be an easier method of implementing dynamic DNS via Google Cloud (Google Domains does not have DNS authentication for wildcard certificates). #!/bin/bash DNS_ZONE= DNS_RECORD_NAME= DNS_RECORD_TYPE=A DNS_RECORD_TTL=300 PATH_TRANSACTION=/root/.config/gcloud PROJECT_NAME= DNS_RECORD_OLDDATA=$(docker run --rm -e CLOUDSDK_CORE_PROJECT=$PROJECT_NAME -v /mnt/user/appdata/gcloud:/root/.config/gcloud google/cloud-sdk gcloud dns record-sets list --zone=$DNS_ZONE --name=$DNS_RECORD_NAME --type=$DNS_RECORD_TYPE | grep $DNS_RECORD_NAME | xargs | cut -d\ -f4) DNS_RECORD_NEWDATA=$(curl ifconfig.me) if [[ $DNS_RECORD_OLDDATA != $DNS_RECORD_NEWDATA ]]; then DEFAULT="--zone=$DNS_ZONE --transaction-file=$PATH_TRANSACTION/gcloud-dns-transaction-$(date +%s).yaml" docker run --rm -e CLOUDSDK_CORE_PROJECT=$PROJECT_NAME -v /mnt/user/appdata/gcloud:/root/.config/gcloud google/cloud-sdk gcloud dns record-sets transaction start $DEFAULT docker run --rm -e CLOUDSDK_CORE_PROJECT=$PROJECT_NAME -v /mnt/user/appdata/gcloud:/root/.config/gcloud google/cloud-sdk gcloud dns record-sets transaction remove $DEFAULT --name=$DNS_RECORD_NAME --type=$DNS_RECORD_TYPE --ttl=$DNS_RECORD_TTL $DNS_RECORD_OLDDATA docker run --rm -e CLOUDSDK_CORE_PROJECT=$PROJECT_NAME -v /mnt/user/appdata/gcloud:/root/.config/gcloud google/cloud-sdk gcloud dns record-sets transaction add $DEFAULT --name=$DNS_RECORD_NAME --type=$DNS_RECORD_TYPE --ttl=$DNS_RECORD_TTL $DNS_RECORD_NEWDATA docker run --rm -e CLOUDSDK_CORE_PROJECT=$PROJECT_NAME -v /mnt/user/appdata/gcloud:/root/.config/gcloud google/cloud-sdk gcloud dns record-sets transaction execute $DEFAULT fi Anyways, thats my rabbit hole for today... cheers. dnsupdate.sh