Lately, I have been experiencing problems due to the mutual distrust between MaxCDN and GoDaddy. The issue develops exactly as follows. To facilitate access to the site from every point in the world, the images, js, css, and html files I sent to MaxCDN’s servers are processed through certain IPs. Up to here, everything is normal.
However, due to an unexpected recent development, GoDaddy hesitates to whitelist some of MaxCDN’s IP addresses because they do not trust them or fear it might create a security vulnerability according to them.
I have 2-3 solutions in mind. These are:
[ol]
Getting a private server through GoDaddy and taking full responsibility to get MaxCDN IPs whitelisted.- Changing the hosting company (Last resort)- Canceling MaxCDN membership and turning to alternatives like CloudFlare or Amazon. (I would greatly appreciate it if you could share your good or bad experiences regarding the Cloud system or Amazon’s CDN.)[/ol]
I am eagerly awaiting extra, easier solutions from you. Thank you in advance to everyone for their help.
GoDaddy is good for domains. For servers, I recommend you look at one of DigitalOcean, Vultr, or Linode. If you aren’t getting a VPS but a direct server and your budget is low, look at SoYouStart, an OVH sub-brand; you can get a dedicated server for 30 euros. If you have an even lower budget, look at Kimsufi, another OVH sub-brand. If you say “I pay 70-80 euros monthly, pay a one-time setup fee of 2 euros for up to 256 IPs, and host my network of 100-150 sites with 100-150 IPs here,” you can handle this business for fees like 80 euros like me. (Kimsufi 16, SoYouStart 16, and the main OVH site give the right to purchase 256 IPs per server. You pay 2 euros once per IP, you do not pay monthly afterwards. As for the connection, Kimsufi and SoYou provide 250mbit or 100 mbit non-shared, and at OVH you buy from 250 mbit up to 10 gbit depending on your budget, which is also non-shared.)- I mentioned it above.- I recommend using Cloudflare if you have the potential to receive attacks. MaxCDN is a large company and has a TR PoP point. So, files are served to your visitors from TR. If you reach out and explain your problem, they will solve it. I used MaxCDN and CDN77 for a long time. Both have PoP points. I switched from MaxCDN to CDN77 because it could be used on unlimited sites. Later, I started taking on big jobs directly with the Amazon CloudFront service. There too, you pay for what you use, and I think it is quite successful. In fact, currently seocry is completely on Amazon. Mail infrastructure: Amazon SES, CDN infrastructure: CloudFront, DNS infrastructure also uses Amazon Route 53.[/ol]
I spoke with MaxCDN customer service; since I currently live in Canada, I cannot connect directly with those in Turkey. However, the information they conveyed to me was along these lines. Apparently, many people are experiencing issues with the IP addresses blocked by GoDaddy. In fact, the GoDaddy situation has reached the point where they suggest using a different CDN company. They stated that there is nothing to be done for such a situation unless GoDaddy whitelists the IPs. This became a bit like CDN gossip, but that is how the situation is progressing.
I really appreciate the suggestions. I really can’t be bothered to change servers right now I will talk to MaxCDN again and relay the developments to you. I hope an outcome that is beneficial to everyone emerges.
After a rough night, as a result, I decided to remove MaxCDN, get by with Cloudflare for a while, and then continue by switching to a dedicated server. However, a problem occurred on the site; despite removing the CDN in the plugins and clearing the caches, there is confusion because media items (images, PDFs, etc.) are still trying to be pulled from the CDN. Because of this, it constantly gives errors while loading media. Clearing CDN caches via the database could be a solution, but since the database is very sensitive, I see that as a last resort. Do you have any solutions in mind?
Friend, I would like to share the experience and knowledge I gained regarding this problem with you. If the CDN is still active on your page even though you removed it, I recommend checking the function.php file, as the problem might stem from the database. Because in my case, thinking it originated from plugins, redirects to subdomains were added in the function file. You can solve the problem by replacing the subdomains with your normal link.
Another potential source of a similar problem could be the .htaccess file. You can solve similar problems by checking the rewrite settings there. I hope this becomes a useful solution