frakman1

To get this to work on my Windows 10 (Enterprise) I had to set AllowInsecureGuestAuth to 1 in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] in the Registry Editor. Then I had to login with username "\" and no password.

Can you please change the template to use br0 instead of eth0 by default? It doesn't work otherwise and that's the default interface for most Unraid users and I would never have known to change this without spending way too much time trying to figure out which interface (out of dozens) to use and if I had to change the network from host to bridge etc. This should work 'out-of-the-box' without any fuss.

Once you get your C prompt, did you try running the three commands in the comment above?

Is there a workaround that doesn't involve having to generate a new key? I'd like to continue using the same key I have on the various different machines that I connect from. I just upgraded from 6.9.2 to 6.10.3 and can no longer ssh into my Unraid server from my MacBook Air (High Sierra) I realize that the algorithm I use is outdated (2048 SHA256). My pub key in the Users->root>SSH authorized keys starts with ssh-rsa. I changed the ending comment to read [email protected] where Tower is the hostname of the Unraid server as the comments above suggested but it still doesn't work. I tried this: (since -oPubkeyAcceptedAlgorithms was not recognized on my system) (tower is set to my IP address in /etc/hosts) ssh -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedKeyTypes=+ssh-rsa [email protected] ssh_exchange_identification: Connection closed by remote host I tried changing sshd_config on the server to include these options based on some post I saw online: RSAAuthentication yes PubkeyAuthentication yes HostKeyAlgorithms=ssh-rsa,[email protected] PubkeyAcceptedAlgorithms=+ssh-rsa,[email protected] in /boot/config/ssh/sshd_config and restarted the ssh server using /etc/rc.d/rc.sshd restart But that didn't work. I then found that ssh'ing from my modern M1 MacBook Pro (ventura) worked. I then reverted all my server changes including the comment at the end of the public key. ssh still worked from my new MacBok Pro. I also confirmed that it works from my Ubuntu 18 machine. Is there anything I can do to enable SSH from my old MacBook Air on High Sierra (macOS 10.13.6)?

I don't know but a Google of the error message took me to this forum discussion: > Initializing to bash, running gitlab-ctl reconfigure (waiting for the db to fail, then start accepting connections, which took ~12 minutes for me) and then running reconfigure again allows it start.

You can limit log file sizes by changing the environment variable in your Edit docker template page. Mine looks like this. I disabled prometheus because it's a giant hog. --log-opt max-size=10m --log-opt max-file=1 --env GITLAB_OMNIBUS_CONFIG="external_url 'http://MY-UNRAID-IP:9080/'; postgresql['shared_buffers'] = '256MB'; sidekiq['concurrency'] = 15; prometheus_monitoring['enable'] = false;"

You right click on the GitLab-CE entry in the Docker tab of the UnRaid webpage, then select Console Hope that helps!

Unfortunately, I'm not sure I can help with your specific setup as I have it configured very differently. I use Cloudflare for my DNS and Let's Encrypt for the SSL certificate management within NginxProxyManager. You may need to map my logic to your specific setup. After some trial and error, I was able to get the external URL to work with SSL and have the Clone button in my repo point to the external URL instead of the local IP address: Browser Location bar: Gitlab Clone panel: How come you are setting env variables manually? I put them all as one string under Extra Parameters: I changed external_url to https://mysite.com/ I then made the following changes to gitlab.rb: external_url 'https://mysite.com' nginx['listen_port'] = 9080 nginx['listen_https'] = false and ran gitlab-ctl reconfigure In Nginx Proxy Manager: With the appropriate SSL certificate details for Let's Encrypt The problem I now have is that I am unable to do a git clone on either https or ssh without getting some authentication/SSL error. It used to work when I used the local server's IP address before I changed it to external URL.

I had a similar problem with localhost URL instead of my actual server when I clone. In the docker template page in Unraid, I had to add the external_url parameter to Extra Parameters and set it to my Gitlab WebUI IP:PORT. In your case, you may want to change it to your actual site URL. --log-opt max-size=10m --log-opt max-file=1 --env GITLAB_OMNIBUS_CONFIG="external_url 'http://MY-UNRAID-IP:9080/'; postgresql['shared_buffers'] = '256MB'; sidekiq['concurrency'] = 15; prometheus_monitoring['enable'] = false;" I use NginxProxyManager to manage the internet-facing URL.

I put mine around line 116: I now notice that I use log_format while the file seems to be using log-format. Not sure if it makes a difference. You may want to try both if it isn't working like you expect.

The link to the script shows exactly how it's used. In any case, you don't have to use the script because I already did and provided the output. Those are the three lines you need to copy into the goaccess.conf file.

Thank you for the definitive answer and suggestion. I don't understand where the previous container's digest would be. Doesn't the old container get blown away after an upgrade? The only "inspect" I can run is on the new container. I also thought that an upgrade explicitly removed the orphan image that was the previous "latest" tagged image. I remember seeing that in the logs as the last step of the upgrade process. So after an upgrade, both the old container and the old image are gone and all I have is the new image and the new container created from it. Am I missing something? Maybe there's a misunderstanding. I'm not trying to figure out what version the current "latest" tag corresponds to. Yes, I can compare digests to published values. I am trying to determine the version of the previous version of the app just before the failed upgrade. It was also tagged as "latest".

Unfortunately there is no way of knowing what the version I had running before the upgrade was. Was it the previous version? Was the it the one before that? etc. I don't upgrade as soon as a new release is made so it could be anything in the last year. Is there a log of the docker upgrade operations and associated output anywhere? @Squid It just seems wrong that if I didn't happen to take a screenshot of the docker upgrade popup then it's gone forever.

I have a slightly different but related question. When I upgrade a docker app, there is a pop up with details about the upgrade. After the upgrade completes and I close that window and later find out that the upgrade failed, how do I know what the previous version of the docker image was? It's always set to xxx:latest in the template so there's no way of knowing after the operation completes what it was before. Is this information/log saved anywhere? When filing an issue/ticket against the app, I'd like to know what the source and destination versions where that caused the failure.

Sorry, I misunderstood earlier. I didn't know there was a second 'official' app on Community Applications. I'll have to try is out and get back to you later. UPDATE: Sorry, it's highly unlikely that I will revisit this on a different version of the app. It seems it was added after I started using the one from Grack's Repository. I updated my post to show which version I am using. You can use that one if you like.