Broke Kubernetes From Shell

[DevOps]

I hope your all enjoying your Valentine’s Day.
After searching through all of google I was hopping I could give the community a try.
I am new to Truenas Scale. I’ve been playing with it and now I’ve gotten to a point where I’ve broken it.

The original issue was I installed nextcloud from the repository

I tried forwarding the port so I can remote into it via port 9001

It gave me an error “ error 400 plain http sent to https port” - Googled it found its an Ngnix issue

I tried to see the log but I was given a permission error. “unable to read /etc/rancher/k3s/k3s.yaml”

Found this website that says how to fix it - https://blog.mphomphego.co.za/blog/2021/04/19/note-to-self-error-loading-config-file-k3s.yaml.html

Used the shell to paste in command on Truenas - now apps are not working. Seems like this version is not compatible or something else is going on.

Is there anyone kind enough to look into this, I will continue my trouble shooting efforts. I really dont want to factory restart but I am also willing.

Was hoping I can reinstall a default configuration or something.

 

[Heavy]

Are you logged in as root?

 

[DevOps]

Are you logged in as root?

Yes

 

[Heavy]

Yes

What's the exact command that you ran in the shell that caused this?

 

[DevOps]

curl -sfL https://get.k3s.io | K3S_KUBECONFIG_MODE="644" sh -s -

 

[Patrick M. Hausen]

You broke your TrueNAS installation. Reinstall and start over. You wrote a standard k3s installation over the specifically tailored one that comes with TrueNAS.

 

[Heavy]

Yeah your installation is cooked. Id lookup Truenas specific guides when looking to accomplish specific goals.
Search the forums, join the official discord, lookup YouTube videos, but just don't run commands like that unless you're 100% sure you know what you're doing.

 

[dain]

I had the same problem and found a little less destructive way here: https://www.truenas.com/community/threads/shell-access-to-apps-permission-denied.107099/#post-740809

Code:

sudo chmod a+r /etc/rancher/k3s/k3s.yaml

I needed it so that I can prod Photoprism to re-index on a cron schedule where running `sudo k3s kubectl ...` wouldn't have worked.