Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About DennyS

  • Rank
    Junior Member
  1. Thanks for the info on clearing the cache in db, however everything seems to be working this morning! green locks! After i made changes yesterday and re-ran the cron job a few times i was still seeing red locks. Perhaps the normal cron run updated the cache in db? I solved my issue by Installing Curl 7.64.0 and recompiled Apache. In the curl section of PHP info page im now seeing correct version of Curl with OpenSSL/1.0.2k ! Also i did update my configuration.php with ; $mysql_charset = 'utf8'; since without it, the cron command below was throwing all kinds of errors about db collation being latin1. Did the db collation for those tables change somewhere between 7.1 to 7.7 ? i was previously on 7.1 php -q crons/cron.php do --SslSync -vvv have a good one!
  2. yes i had alot of issues too but finally got everything resolved. please post your errors and lets see πŸ™‚
  3. WoW thanks @ju5t ! I had collation errors, red everywhere. My I added the $mysql_charset to configuration.php and reran the cron below and no errors this time. However still red locks everywhere? php -q crons/cron.php do --SslSync -vvv WHMCS Automation Task Utility: do ================================= Queuing Tasks ------------- Force run any tasks: ignore "in progress" and "is due" Task queues ready Executing Application Queue --------------------------- 0/1 [β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘β–‘] 0% < 1 sec/< 1 sec 26.0 MiB SSL Sync 1/1 [β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“β–“] 100% 4 mins/4 mins 26.0 MiB Executing System Queue ---------------------- No tasks to execute in queue [OK] Completed
  4. Adding... using your curltest php script. #cat curltest.php <?php $url = "https://www.webhosting-canada.net/index.html"; $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, $url); curl_setopt($ch, CURLOPT_TIMEOUT, 10); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); $data = curl_exec($ch); echo "CURL Connection: "; if (curl_error($ch)) { echo "ERROR ".curl_error($ch)."<br><br>"; } else { echo "SUCCESS<br><br>"; } curl_close($ch); echo "Data:<br><textarea rows=\"20\" cols=\"120\">$data</textarea>"; ?> [root@bs1 public_html]# php curltest.php CURL Connection: SUCCESS<br><br>Data:<br><textarea rows="20" cols="120"><!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="https://webhosting-canada.net/index.html">here</a>.</p> </body></html> </textarea>#
  5. Hi John, there is no error in Curl. red lock in whmcs curl -v https://webhosting-canada.net * About to connect() to webhosting-canada.net port 443 (#0) * Trying * Connected to webhosting-canada.net ( port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 * Server certificate: * subject: CN=webhosting-canada.net * start date: Mar 11 19:57:47 2019 GMT * expire date: Jun 09 19:57:47 2019 GMT * common name: webhosting-canada.net * issuer: CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US > GET / HTTP/1.1 > User-Agent: curl/7.29.0 > Host: webhosting-canada.net > Accept: */* > < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Wed, 13 Mar 2019 19:05:25 GMT < Content-Type: text/html; charset=iso-8859-1 < Content-Length: 248 < Connection: keep-alive < Location: https://webhosting-canada.net/index.html < <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="https://webhosting-canada.net/index.html">here</a>.</p> </body></html> * Connection #0 to host webhosting-canada.net left intact
  6. I got this fixed. i believe it was caused by an old modules not compatible with php7. check your modules!
  7. DennyS

    SSL Monitoring does not work.

    Bingo! yes we should be able to choose whether we want this or not. No change on my end with 7.7.1 and curl works fine on my server returning proper ssl info for all valid certs. But still showing clients they have no ssl! frustrating. Has anyone figured out a quick solution? do we really need to edit the templates?
  8. DennyS


    LOL no i dont think so! But Modules Garden has implemented a few!
  9. DennyS


    Hi Everyone, Im new to the forums but not whmcs, been using it since v5.x and have contributed to the Feature Requests. Looking forward to being more involved here with the community. Thanks! Denny
  10. I am running version 7.7.1 and this red padlock is still an issue. Why did you not give us the option to disable this? This is causing confusion from our customers and we look like idiots. My curl on the server is fine and does not return any errors. Its your code thats wrong. All of our customer sitessites that have SSL certificates are showing up with the red padlock! unacceptable. So can we have a proper solution now? please provide a hotfix to clean up this mess.
  11. Hi, Trying to update version with a full zip upload. After uploading all files, refresh admin page & client page and we get a blank page. Found error below in Apache error log. [Wed Jan 30 10:54:07.593213 2019] [fcgid:warn] [pid 17292] [client] mod_fcgid: stderr: PHP Fatal error: Interface 'Whoops\\RunInterface' not found in /var/www/clients/client1/web7/web/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php on line 0 Does anyone know what to do to fix this or find the cause? Thanks! D
  12. Welcome to WHMCS.CommunityΒ DennyS! We're glad you're here please take some time to familiarise yourself with theΒ Community Rules & GuidelinesΒ and take a moment to introduce yourself to other WHMCS.Community members in the Introduce Yourself Board.


Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated