Hello,
Do you guys use cdn or cloudflare on your cpvlab installation?
Does it matter?
Well for me the speed matters... so I wanted the pages/php files to load fast...
anyway... my problem is with cache... there were times when I created a few landing pages... and some css/js was cached and I have to manually purge the files so the new ones shows up...
that's just a small portion of the problem...
my biggest problem is... (not sure if it is cloudflare's fault)
There are times... (actually happens 3times already)
when my campaign... is redirecting to a wrong OFFER....
basically the flow is like this:
The correct flow is this:
visitor --> goes to landing page of CAMPAIGN A --> visitor clicks the CTA --> visitor redirected to an offer1 offer2 or any offer that is "INSIDE" CAMPAIGN A
but for some reason 3 of my campaigns are like this:
visitor --> goes to landing page of CAMPAIGN A --> visitor clicks the CTA --> visitor redirected to a random offer OUTSIDE OF CAMPAIGN A
Don't mix a CDN or Cloudflare with your tracking system. Your tracking system is dynamic and there is little scope for caching. In fact, trying to cache such things will likely break functionality and cause problems.
Using CloudFlare/CloudFront in front of a tracking system is advanced stuff and well outside what you want to get involved in.
Thanks Zeno!
I went ahead and added a page rule to my cpvlab installation... hoping this fixes up the problems
The issue here is that you are using a service that caches frequently requested pages to accelerate delivery. The tracking system invariably deals with unique URLs and there is therefore little use for CDN-based caching. If Cloudflare loads a unique link and sees lander A then it caches lander A as the response. You're then screwed if you want to rotate landers. If outgoingclick.php goes to offer A then this gets cached and now all landers send people to the same offer.
You then need to tell CloudFlare to NOT ignore querystrings, so that it treats outgoingclick.php?offer=25 differently to outgoingclick.php?offer=26. However, if you are rotating offers on the backend again you have just screwed things by caching.
Furthermore, the IP of the user will always be CloudFlare and this messes with your tracking. You have to set up header-forwarding rules in your nginx/Apache/etc configuration.
I'm not sure how to spell this out more clearly.... Don't use CloudFlare with your tracking system. It is not going to do what you want it to do.
I have configured Cloudflare to spit the visitor's real IP via Apache...
(this really was a pain long time ago... especially when I try to ban users in my forums... my vbulletin can only ban cloudflare's IP... but they already plugged this loophole... a few months back..)
Anyway... so far the page rules fixes the cache problems and querystrings... I can't test much further though... I ran out of funds... (lol).. on my end... and other virtual machine (with vpns)... the campaigns are working as they should be...
Thanks for your concern though...
If I find any further issue... I will go ahead and get this badboi out of cloudflare... and get a new server...
I am just trying to save my main server's IP from those prying eyes...
I have been a victim of multiple DDoS... every now and then... and I currently only have 1 dedicated server...
(I used to have 9 big dedicated servers... when money was flowing... but now that it isn't anymore... I am left with only 1 server.)
I cannot allow those script kiddies.. to find out my server's real IP... or all my website that making money will be toast!
Are you running CPVlab for tracking on a server which is also hosting other websites that make money by their own means?
well yes... is that going to be a problem?
this is a dedicated server... I own all the sites that is in this dedicated server...
and I still have adsense/medianet websites in this server...
Do you have WordPress installs on that server? If so, I would STRONGLY advise getting a different tracking server. If I had a dollar for every time I'd heard of someone's tracking getting rooted thanks to a wp exploit... Well, I'd have about eight dollars, but that's still too much risk.
Unless you're running huge volume, you could just get a $5 vps and run your tracking on that, avoiding cloudflare and security issues all at once.
Yeah... don't run tracking on the same server. You want to be able to scale tracking independent of other websites and the last thing you want is, as Caurmen says, a WP-related event causing strife with your tracking.
If you aren't running millions of clicks daily you won't need a dedicated server.
Hi caurmen,
yes I have a couple of wp installs... I am pretty sure this server is rock solid and so does my wp installs...
but yeah I guess you are right... I will look into getting a new server for this tracker...
Thanks a lot guys...
Yep!
I will be getting a new server for the tracker...
Thanks again...