How to Fix Failed while decoding JSON: Can't connect to www.example.com:443 error?

SUBMITTED BY: Guest

DATE: Aug. 9, 2019, 10:30 p.m.

FORMAT: Text only

SIZE: 3.2 kB

Raw Download

HITS: 433

Report
  1. How to Fix Failed while decoding JSON: Can't connect to www.example.com:443 error?
  2. Changed domain name and also changed cron values with new domain name. But when trying to transfer files from one server to another, the cron on targeted server doesn't run.
  4. ++++++++++++++++++++++++++++
  5. list of top cheapest hosting http://listtop.pw/
  7. Top 200 best traffic exchange sites http://listtop.pw/surf
  9. list of top gpt sites
  10. list of top ptc sites
  11. list of top ptp sites
  12. list of top crypto currency Wallets sites
  13. Listtop.pw
  14. Listtop.pw
  15. Listtop.pw
  16. +++++++++++++++++++++++++++++
  18. This is CentOS 7 with Webmin installed server.
  20. Gives this error on cron log:
  22. n****** CROND[22775]: (olddomain) CMDOUT (Failed while decoding JSON: Can't connect to http : // www olddomain com:443)
  23. n**** CROND[22775]: (olddomain) CMDOUT ()
  24. n***** CROND[22775]: (olddomain) CMDOUT (Connection refused at /usr/share/perl5/LWP/Protocol/http.pm line 51.)
  25. The above error log simply says still olddomain is somewhere and exist.
  27. I expect to change the old domain with new domain but couldn't find the proper file to edit and target new domain.
  29. you need to provide more info like what is that script you are setting cron for? assuming you searched every file for that domain and didn't find any, may be the script saves the old domain in database (sqlite,mysql, etc...) .
  31. XSL.TEL - A Lonewolf Fully managed hosting provider since 2011
  33. you need to provide more info like what is that script you are setting cron for? assuming you searched every file for that domain and didn't find any, may be the script saves the old domain in database (sqlite,mysql, etc...) .
  34. i cant give the script name.
  36. the database name shows old domain name without .tld . but i dont think thats a problem.
  37. and webmin doesnt have phpmyadmin module, how can i search word inside mysql ?
  39. the file transferring cron of the server simply doesnt run just because some code tries to connect to the old domain name.
  41. Changed domain name and also changed cron values with new domain name. But when trying to transfer files from one server to another, the cron on targeted server doesn't run.
  43. This is CentOS 7 with Webmin installed server.
  45. Gives this error on cron log:
  47. n****** CROND[22775]: (olddomain) CMDOUT (Failed while decoding JSON: Can't connect to http : // www olddomain com:443)
  48. n**** CROND[22775]: (olddomain) CMDOUT ()
  49. n***** CROND[22775]: (olddomain) CMDOUT (Connection refused at /usr/share/perl5/LWP/Protocol/http.pm line 51.)
  50. The above error log simply says still olddomain is somewhere and exist.
  52. I expect to change the old domain with new domain but couldn't find the proper file to edit and target new domain.
  53. If this is VPS or Dedicated Server you can easily find if your site script has old domain mentioned in any file that you have to replace with new domain to get this issue fixed.
  55. To search old domain in files just ssh your server and go to the exact document root of domain and run this command.
  57. easytrafficboost.com
  58. elevatedtraffic.com
  59. 5 hostages killed
  60. majorleaguehits.com
  61. masteriq.net
  62. www.vikinghits.com
  63. Scarlet-Clicks.info
  64. domaine d'arondeau
  65. silverclix.com
  66. host ip
  67. 1 and q hosting
comments powered by Disqus