txwireless

Technical Details: Primarily accessing system running 6.10.0-rc2 from Mac OS 11.6 Big Sur, Safari 15.0. However, issue also presents on Chrome. Using alphaSSL signed wildcard certificate and forced SSL selection under management. Behavior: - If signed SSL is enabled (haven't tested with self-signed), then accessing via IP address or FQDN shows FQDN in address bar with enabled SSL (as expected). - After logging in, when right-clicking on docker container in docker tab - inconsistent behavior between when console/terminal is selected versus logs. Logs pops up a window and logs are viewable (as expected). Console pops up a window which prompts for login again which then takes you to main page. - Console behavior doesn't present issue when SSL not used Diagnosis: - Using web inspector, looked at JS code for console vs. logs which are patterned differently where presumably they should be similar in behavior as the resulting code is pulling from same server versus from another machine, etc. - After reviewing further, noticed under cookies that once the user signs in, a session cookie is created with a name patterned something like unraid_[random alphanumeric string] which appears appropriately for the FQDN with scope of / marked secure and http only. - In the window popped up with the logs, the cookie is present with same value and therefore not requiring authentication - In the window popped up for console which is prompting for identification the unraid_[random alphanumeric string] session cooke is absent (consistent with what the behavior is but not the desired behavior which would be for the cookie to be present and presumably not needing to authenticate again). - Did not take the step to analyze the javascript to see if it is how it is called or if something is stripping it on server side in the code there. Screenshots/Logs: - Did not attach as first time reporting bug and not sure if they are viewable by other users. If not, happy to attach or respond via PM. It should be fairly straightforward to replicate as I've played with it a few times on and off. Priority: - While resolution is likely to be minor, as it limits console access to containers, I selected urgent as other users may not be as comfortable using direct docker commands to gain access to the terminal. Workaround [for other users]: - I know you know this but for other users, if you have setup ssh access to your machine you can ssh in. - With container running use docker ps for a list of running containers, there will be a list of containers with alphanumeric ids. Figure out the first 2 or 3 characters of the id which are unique from any other id shown. - Run: docker exec -it [2-3 character id from above] /bin/sh - This will give you command line access - if you know the container has bash, zsh, ash, etc. you can substitute the full path of shell in the command above where /bin/sh is - Note: you can run also simple things like ls -al /bin where /bin/sh is above and it'll show you everything in your bin directory in the container if you don't know what shells are present - docker exec -it [2-3 character id from above] ls -al /bin - If you use a shell to get into the console, use exit to return to the unraid host shell from the container shell