During an exchange and discussion with a blogger, I suddenly found that the support function that my site originally planned to allow HTTP to forward HTTPS did not actually take effect. If you enter the domain name directly, an error page of 400 will appear. At the beginning, it took a lot of energy to make the whole site support HTTPS, but I didn’t expect this result.
In the afternoon, when I started the commonly used virtual environment, I found that the progress bar would not move for a long time in the middle, which was not normal. In the past, I could see the desktop in 10 minutes at most. Click the direction key on the keyboard to view the printed log. The bug information shown in the following figure is repeated all the time. Even after waiting for more than half an hour to enter the system, the log information is continuously output on the terminal interface.
Recently, there was a problem with the local virtual machine, but a new environment was rebuilt. As a result, when logging in to the terminal with mobaxterm tool, it was found that you had to wait 4 ~ 5 seconds to enter each time. The operation inspection was not very good. I don’t understand why the local environment connection is so slow, so I still have to find a way to analyze it.
Some netizens have similar puzzles, suggesting that it may be the reason why they need to address through DNS during SSH login. Refer to the article to find
/etc/ssh/sshd_config sets the
UseDNS configuration item to' no ‘, but it is found that it is closed. What causes that?