so all you need is a usb stick with a windows 10 installer, boot to that, click “Repair my pc” after it asks you for the language -> open the troubleshooter -> open the command line interface
then switch to the C drive
then cd Windows\System32\
rename osk.exe osk.old|
rename cmd.exe osk.exe
close and boot windows normally
click the On-Screen-Keyboard which now opens cmd.exe
net user “username” *
type new password
make sure undo your rename of the cmd.exe and osk.exe things after you’re done
This of course, made me extremely nervous. Luckily this only meant that my docker file got corrupted. It happened most likely while I was moving it while the docker service was still active. Yeah, it happens.
Solution:
It’s fairly simple, but it takes a little bit of time.
Go to Settings -> Docker -> Enable Docker, and set to No, then click the Apply button (this disables Docker support)
Go to the location of your docker image and rename the file to docker.img.bak – The file may be in
/mnt/user/system/docker
I’m asking you to make a backup, because in all cases, safety first. “Why didn’t you have a backup in the first place?”, I hear you say. Yeah yeah, we all make mistakes every so often! D:
Go to Settings -> Docker -> Enable Docker, and set to Yes and this creates a fresh and empty Docker image. The docker service should now be started. You can see this as this on the docker settings page:
and on the dashboard you should now see an empty docker field.
Now go to the Apps Tab, Previous Apps Section. Then check off all of your previous applications and hit “Install”
I recommend to do it one by one so you can double-check the settings and clean up the unused templates after you’re done. If you want to make a copy of the templates, FTP into your server and go to
/boot/config/plugins/dockerMan
After you have restored your docker apps, you’re done. Check all the things and make a backup 😉
Virtualmin is a rock solid control panel for your VPS, it’s simple as that. It’s sometimes not so simple to set it up correctly due to its many options.
I’ve tried my best to make a decent manual that explains how to set up a domain and email in a quick and dirty way. I’m not talking about security and stuff yet. It’s just about setting things up.
I am also assuming your freshly (re)built VPS has a root password set and that you are now ssh-ing into it. If not, do it now.
First thing you need to do is find the name of your network interface
Press Y and enter to continue. It will now do the thing. Patience, young one. Phase 1, 2 and 3 should all install without a hitch. [ OK! ]
While you are waiting, go set up the DNS at your registrar.
@ 1000 MX 10 mail.domainname.tld
* 1000 A 0 VPS_IP_ADDRESS
@ 1000 A 0 VPS_IP_ADDRESS
ftp 1000 A 0 VPS_IP_ADDRESS
localhost 1000 A 0 127.0.0.1
mail 1000 A 0 VPS_IP_ADDRESS
pop 1000 A 0 VPS_IP_ADDRESS
www 1000 A 0 VPS_IP_ADDRESS
Don’t worry about the SPF, domainkey, the acme-challenge and the dmarc yet.
If you get “Device “link” does not exist.”, type in the name of the network interface you found at step 1
All should be ready now and you should see a few success messages. If not, go fix.
Time for a little maintenance.
apt-get update
apt-get upgrade -y
apt-get dist-upgrade -y
apt-get autoremove
apt-get autoclean
RESTART THE VPS
To the control panel mobile!
https://HOSTNAME:10000
Log in with your root password
You will now have to go through the post-installation wizard, press Next
Set everything up to according to your wishes. For me, that’s:
Preload Virtualmin libraries? yes
Run email domain lookup server? yes
next
Run ClamAV server scanner? yes
next
Run SpamAssassin server filter? yes
next
Run MariaDB/MySQL database server? yes
Run PostgreSQL database server? no
next
Set a MySQL password. Make it strong!
MariaDB/MySQL configuration size:
next
Primary nameserver : YOUR_HOSTNAME and tick the checkbox “Skip check for resolvability”
next
Password storage mode: Only store hashed passwords
next
Virtualmin post-installation configuration is now complete!
next
Are we done yet? D: No.
Click “Re-check and refresh configuration”If you get
Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page.
Click list of DNS servers and add 127.0.0.1 in the DNS Servers field and press Save. Next, click Apply Configuration. Then, click the Virtualmin on top, click System Settings and then Re-check Configuration.
No errors? Click Return To Virtual Servers List
Your Virtualmin installation is now ready to had domain names etc added.
Set up your first virtual server
Click Add New Virtual Server, Owned By: <new user>
Enter the following data:
Domain name: YOUR_DOMAINNAME.TLD
Description: Optional, but make a short desc.
Administration Password: STRONG_PASSWORD!Under Enabled Features tick the options you would like to have. I basically tick everything except for “Setup IP-based virtual FTP” since I don’t need it.
Click Create Server
If all went well, click Return To Virtual Server Details where you can check things again
Time to install a SSL certificate for your domain
Is your domain available already under simple http://? If you have moved your domain and changed your DNS, ping your domain as well to see if everything is set correctly and has been propagated completely. Your frontpage of your domain should say “Apache2 Debian Default Page”
Time to make some DNS additions! Click Server Configuration and then click DNS Records.
Move the following data over to your DNS settings at your registrar:
SPF, _acme-challenge.mail and _acme-challengeSo, here’s an example:For SPF:
When everything is set up, go to the Virtualmin tab, click Server Configuration and then click SSL Certificate
Click Let’s Encrypt
Did you set up your DNS according to the pre-filled list you see in the field named “Domains associated with this server”? Then you’re good to go and click Request Certificate. If not, manually enter the domain and subdomains.At this point, the request either succeeds or fails. In the latter case, click SSL Certificate again, then Let’s Encrypt and correct the wrong entry.TIP: If you have errors and try to get a certificate too many times, you get an error about that as well. If you get the following message, go play outside for a little bit or proceed with setting up email as described in the next part.
Error requesting challenges: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/
dfdsfsf
Setting up e-mail
Click the Virtualmin tab, then Edit Users
Click + Add a user to this server
Enter a mailbox name, like “info”
Enter a password
Click the Create button
Now this has been set up, you can poke your DNS settings again! Woo!
Click the Virtualmin tab, then Email Settings, then DomainKeys Identified Mail
Click Install Now and wait
At the bottom of the page, it should read
installation completed successfully
Click Return To DKIM Form
Set the DKIM up as follows:Signing of outgoing mail enabled? yes
Selector for DKIM record name: 2018
Reject incoming email with invalid DKIM signature? yes
Size of new DKIM key: 2048Press Save when done
All should be well, so click Return To DKIM Form
Click Return To Virtual Servers List
Click the Virtualmin tab, then Server Configuration, then DNS Options
Set this form up as follows:SPF record enabled? yes Allowed sender hostnames: DOMAINNAME.TLD
DMARC record enabled? yesPress Save when done
Click the Virtualmin tab, then Server Configuration, then DNS Records
Copy the _dmarc entry over to your DNS settings at your registrar
Click the Virtualmin tab, then Email Settings, then DomainKeys Identified Mail
Set “Signing of outgoing mail enabled?” to yes
Click the Save button
Click Return to DKIM form
Copy part of the content of the field “DNS records for additional domains” over to your DNSExample:
2018._domainkey IN TXT ( “v=DKIM1; k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAq8/I4PwduFS/q”
“U4y6pDFNFYf868Z2p+BNw+QRMphZ6YnVt1MWeVtNIXnYvhUtf6jhAX2BZ5gl8R2ILyL9NCkFe8W5cAVR”
“/cZkZl6OIc7fdTiLePYNCS3HcVcTiE0Szb3zwDRAZE2XyAqFvNQJuVe/H5tJxlOAu1vhqv3FuZM1viv9”
“VfiPQ77oQ9eOmQMZH59+QL/Vw4fnUnui4QhqRaH+iLb1bQdcJqIu1y3M+bgSCmrSu7v40V1G+wmUY13J”
“fg41SIvYbuEe+CGjwMjVW0KFC15x3m5ChwM3q68b5gBv0L+JeMG27+DDQ5CSUIZSAJU0XifyeAfTIfRe”
“5L+Bec7hQIDAQAB” )This will end in a train wreck, so remove the first part, namely:2018._domainkey IN TXT ( …. )
WARNING. As explained on the “About” page that this is a blog based on my notes, whether they fail or not. So proceed at your own risk.
My Zyxel router currently has firmware version 1.00(AAKL.14)C0 and since Zyxel is a good boye, they keep their devices up to date. Like all manufacturers should do IMO.
Aquire all the firmware files that are available by going to ftp://ftp.zyxel.com/VMG8324-B10A/
Remove the files that are older than your current firmware, in my case v.14
BACK UP YOUR CURRENT FIRWARE AND SETTINGS
Apply ALL updates one by one. Do not skip versions.