Ok … here’s the deal … trying connect to Cockpit throws the following errors (redacted) … Errors first just in case someone can say "Well you id10t you don’t have “this” package installed …
windeath:/home/dart # journalctl -b 0 | grep tls
May 04 18:18:47 windeath cockpit-tls[3420]: cockpit-tls: connect(http.sock) failed: Permission denied
May 04 18:18:56 windeath cockpit-tls[3420]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
May 04 18:20:56 windeath cockpit-tls[3736]: cockpit-tls: connect(https-factory.sock) failed: Permission denied
And before anybody grouses I run as user:dart (not root) and have 1 terminal open su’ed to root because I get tired of typing “sudo” all the time 
Now … back to the info … I install from the repos
windeath:/home/dart # zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
--+----------------------------+--------------------+---------+-----------+---------+------+----------+--------+--------------------------------------------------------------------------------+--------
1 | OpenH264 | OpenH264 | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed |
2 | Packman-essentials | Packman-essentials | No | ---- | ---- | - | 99 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials |
3 | openSUSE:repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://cdn.opensuse.org/tumbleweed/repo/non-oss?mediahandler=curl2 |
4 | openSUSE:repo-oss | repo-oss | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://cdn.opensuse.org/tumbleweed/repo/oss?mediahandler=curl2 |
5 | openSUSE:update-tumbleweed | update-tumbleweed | Yes | (r ) Yes | Yes | - | 90 | rpm-md | https://cdn.opensuse.org/update/tumbleweed?mediahandler=curl2 |
6 | src-oss | src-oss | No | ---- | ---- | - | 99 | rpm-md | https://download.opensuse.org/tumbleweed/repo/src-oss?mediahandler=curl2 |
The current install is without any modules (in case they were causing a problem) … apparently not … I followed the procedure that @sfalken provided Here
Things I’ve tried:
- Set my router to IPV4 only and IPV4/IPV6
- Did the same on my local machine
- Tried both HTTP and HTTPS
- Tried both localhost:9090 and 192.168.1.119:9090
- Tried Floorp (FireFox fork), Chromium, Falkon and (Edge (Win10 x86_64)) from my new/old laptop with both HTTP and HTTPS
- Went through my SELinux setup with Yast (and enabled AppArmor because it told me too) … file permissions set to “permissive” when enabled currently disabled
- Checked my /etc/hosts file
All browsers grouse about not having a proper TLS certificate and when tell them to “proceed, I understand” the next message is “connection reset” and I’m done
I also made a new user “Mr. Clean” with username:clean and absolutely no configuration at all … same results and errors
- CUPS and logging into my router work fine on my local network