-
tomahawk1277 started following [6.9.2] VM Disk Capacity Stuck at 2T
-
[6.9.2] VM Disk Capacity Stuck at 2T
I had a Win10 VM working with a disk capacity set to 80G. I tried increasing it to 180G through the webGUI (by clicking the VM name and modifying the Capacity value) but accidentally typed 1800G (an extra 0) and hit enter. It refreshed the page and showed 2T and I cannot change it anymore. No matter what I type there, whenever I press enter it changes back to 2T. Tried rebooting but no dice. My VM will run, and Windows simply sees the extra 1.7T unallocated space in Disk Manager, but I still need a way to change the capacity from 2T to a real number so I can expand my VM disk space. Thanks. diagnostics-20211015-1434.zip
-
[Support] GitLab-CE
That worked, Thanks Saarg! Manually specified a few tagged version numbers from one upgrade to the next until I was able to get the latest. Thanks for the help.
-
tomahawk1277 started following [Support] GitLab-CE
-
[Support] GitLab-CE
Just updated my docker today to the latest (it was a couple months old) and now it's not starting correctly. I am getting this error in the log: * bash[migrate gitlab-rails database] action run [execute] rake aborted! Your current database version is too old to be migrated. You should upgrade to GitLab 11.11.0 before moving to this version. Please see https://docs.gitlab.com/ee/policy/maintenance.html#upgrade-recommendations] Do I need to bash into this docker and manually upgrade the Gitlab core? I had assumed the docker would take care of any upgrades needed. Thanks.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Ah! Mine didn't have the include line for some reason. It recognizes the stream command now. Thanks aptalca!
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Hi all, I'm trying to use the nginx module called "ngx_stream_core_module" (available since version 1.9.0) but it doesn't seem to be enabled in this Letsencrypt docker. The man page says it's "enabled with the --with-stream" option. Is that something I have control over in the docker? The reason I want this module is to forward non-http ports to different IPs (yes, just like my router does, but with the added ability to filter out certain things or block file access). Thanks!
tomahawk1277
Members
-
Joined
-
Last visited