I have a 2 node HA Hyper-V cluster running the full OS (not Core). While logged into the physical node with a domain admin account, i open the Hyper-V console and look at my Guest VMs i can see the status in the preview windows. If i try to open a connection to the guest (Virtual Machine Connection) after about 1-2 min i get the following error messages:
“Cannot connect to the virtual machine. Try to connect again. If the problem persists, contact your systems administrator.”
Solution related to DNS & Hosts file. The host machine you are on must be able to resolve its host name to its own ip address.
to the c:\windows\system32\drivers\etc\hosts file of the host System.
The MatterControl data folder location is not able to be changed; it is set to C:\Users\$USERNAME$\AppData\Local\MatterControl in Windows, ~/.local/share/MatterControl for Mac OS X and Linux.
Adding custom folders from your hard drive
To do this, create a file called
LibraryFolders.conf in the MatterControl data folder location directory. Add the full path to the folders you want to track on separate lines…
Never use unencrypted protocol like HTTP or FTP toward your router!
Your password will travel plain-text and risk is not worth 5 minutes it takes to enable TLS encryption!
For HTTPS to work need to create two certificates (root and HTTPS certificate):
add name=root-cert common-name=MikrotikRouter days-valid=3650 key-usage=key-cert-sign,crl-sign
add name=https-cert common-name=MikrotikRouter days-valid=3650
sign ca=root-cert https-cert
The example is 10 years (3650 days). But this could be less, not a bad idea, changing the cert every year…
If there is a change in the affected package during the firmware upgrade, it is worth re-generating the certs.
With certificate signed, just need to assign it to www-ssl service and enable it, while disabling http:
set www-ssl certificate=https-cert disabled=no
set www disabled=yes
Project done, now you can access your router via HTTPS…
Click anywhere on the page and type a BYPASS_SEQUENCE:
thisisunsafe” is a BYPASS_SEQUENCE for Chrome version 65
badidea” Chrome version 62 – 64
danger” used to work in earlier versions of Chrome
If it not work, check if they changed it again, go to latest Chromium Source Code:
At the moment it looks like that:
var BYPASS_SEQUENCE = window.atob('dGhpc2lzdW5zYWZl');
You can run following line in a browser console:
• At Dell splash screen press F11 to select Boot Manager
• This is the trick, in Boot Manager select Harddisk <Slot 1 RAID: #0100 ID4F LUNO Dell Virtual>
• The next screen will be the option of USB Flash Drive or Harddisk. Select USB Flash Drive.
append to /etc/postfix/main.cf:
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_tls_security_level = secure
smtp_tls_mandatory_protocols = TLSv1
smtp_tls_mandatory_ciphers = high
smtp_tls_secure_cert_match = nexthop
smtp_tls_CAfile = /etc/pki/tls/certs/ca-bundle.crt
relayhost = smtp.gmail.com:587
chmod 400 /etc/postfix/sasl_passwd
chown postfix /etc/postfix/sasl_passwd