-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Used to work but now container cannot start after new build #16
Comments
Have you made sure Proxmox is fully up-to-date? Will |
I'm having a similiar issue, I'm running version 6.1-3. It will install with no errors but, after I login, this is displayed "Clean up process", "No screen session found" (does this 4 times). Closing AP and exit with code:0, then prompts me to logon again. P.S it does enable Samba. |
Please update Proxmox - 6.1-15 is the latest. Also, this will occur if you have not correctly set up the community edition - commonly referred to as the "nag" removal also.
|
Tollbringer, when I run the "apt --reinstall install proxmox-widget-toolkit" command after updating the "pve-no-enterprise.list" and "/etc/apt/apt.conf.d/no-nag-script" files with the information you have provided, I am presented with "E: Syntax error /etc/apt/apt.conf.d/no-nag-script:2: Extra junk after value". I have rebooted the server and also ran it in incognito with the same results. |
If you are around Discord I would love to help. Dr.Zzzs or DigiblurDIY channels! |
Ok, I will login , when I get home. |
I've used your wonderful script before and it worked perfectly.. However I've tried multiple times today and even though it appears to build without error it fails to start with the following erroor:
Trying to run the container in foreground mode didn't really give me much more:
Any ideas as to what the problem might be?
Thank you in advance.
Regards,
Michal
The text was updated successfully, but these errors were encountered: