am
amazy
@amazy
2topics
14posts
joined
last seen
Recent topics
Recent replies
SSL still www.example.comYes DNS works and I am on latest 1.7.3 versionSSL/HTTPS issue after 1.7.3 upgrade and clean install.@jdiggity81 Maybe it could be an issue on let's encrypt side because of too much SSL cert generation but I have this issue from 1st time try so i don't think itSSL/HTTPS issue after 1.7.3 upgrade and clean install.as stated before the certs are added in vhost conf correctly. It's just the SSL generation that is not working. Using certbot instead is not a problem for me buSSL/HTTPS issue after 1.7.3 upgrade and clean install.HI @usmannasir When check CP main log file about SSL issue I have this output after 3 clean 1.7.3 install on the same server as before: [01-43-30-Tue-Nov-2018] SSL/HTTPS issue after 1.7.3 upgrade and clean install.Hi Usman. No I'm on Vultr. Never had any of these issue on the same server with CP 1.7.1SSL still www.example.comExactly the same hereFile Manager Error: Showing loading spinner only, but no result or alert of any errors.same issue here, no changes made to vhost or rewrite rules.Cannot not login to panel via port 8090 after 1.7.3 updateBut this wasn't the case before 1.7.3 right? Because this creates lots of troubles as even my wp pass contained such characters... Anyway, I found a way to overCannot not login to panel via port 8090 after 1.7.3 updateI am 100% sure there is an issue with passwords containing characters used in programming. Prior to 1.7.3 such passwords were accepted. I used a password generaCannot not login to panel via port 8090 after 1.7.3 update@usmannasir if in the future release there is a possibility to update from the panel directly or automatically would be more convenient. There is an issue when