Cockpit-WS startup

Apps and Virtualization
1

Hi everyone!

I feel like I should not have to ask this, but I have been trying to figure out how to start cockpit-ws now that I have it installed.

I have a screen that asks for a username and password, and then a “connect to” entry. I have tried every combination of my IP and server name to get it to connect and it keeps giving me the error:

Not Found

What am I missing? I have searched the help files on this, and I have found no references to a login screen with the “connect to” entry.

Thanks in advance.

Jonathan

2

use the username and password that you use for an SSH connection. The IP is the address of the server you want to connect to. It is equivalent to you terminal in to the server with an ssh account.

1 Like
3

Thanks for that! I will try it right away and get back to you!

4

So, here was what I needed to do:

Enable SSH (I had not needed it so I never enabled it)
Add the truenas_admin login to the SSH permissions
and then I was good to go!

Now, a follow-up question: How do I enable get past “limited access mode” it seems to need the sudo password, but it doesn’t give me an option to enter it.

Thanks for all your help so far!

Jonathan

5

Are you trying to administer Truenas with cockpit? I only used cockpit to admin other devices. I’m not sure the truenas system will be amenable to you using cockpit. It tries to administer itself and itself only. Hadn’t thought about doing that. Interesting.

6

Yeah - I am.
Currently I am spinning up a new truenas box, and it randomly shuts down. It feels like a hardware issue because the same box did it with Proxmox was installed. I was hoping I could find an easier way to view the system logs and try to understand just what goes on when it fails. It seemed like an easy interface to try and cross reference the logs easier and figure it out.

Unfortunately, I am not an expert on this type of thing - I am moving from a standard user to a HomeLab experimenter!

Thanks for all your help, I appreciate it!

7

IMG_3873
IMG_38734032×3024 2.49 MB

So, I finally captured the failure occurring.

This is an example of what comes up on the console.

I have been trying to decipher it, but I am not having much luck. Does this look familiar to anyone?

Thanks

Jonathan