- Joined
- Jul 1, 2016
- Messages
- 6,571
- Reaction score
- 2,582
Was the PBX on-prem?Hello
we've had a customer on 3CX for over year or so with no issues.
They've been bought out and donkey IT are taking over.
We gave them a 3CX backup and wonder if they're causing this issue.
But, this is the issue..
View attachment 35592If we ping the FQDN it comes back with 1.1.1.1
No its in OVH with 3CX FQDN.Was the PBX on-prem?
Looks like WAF in Cloudflare, like they proxy their FQDN through it.
They definitely did something wrong somewhere.No its in OVH with 3CX FQDN.
dont know what they've done with the backup like.
Customer is off-boarding to them so i'll let them sinkThey definitely did something wrong somewhere.
I would get on a remote session with them and redo the whole process to be sure they aren't screwing up because they don't know squat about 3CX.
I wouldn't but you do you lolCustomer is off-boarding to them so i'll let them sink![]()
They can come back to us if their new provider isI wouldn't but you do you lol
idk but I know it wasnt me. Just annoys me that I have to waste my time sorting their incompetence.My first thought was as per ConceptsWeb, that they were trying to proxy through Cloudflare. But this should not be possible because they wouldn't have been able to validate a 3cx domain in Cloudflare and change the NS setup...
My $0.02 - someone who doesn't know what they are doing has set their static public IP address to 1.1.1.1 in 3cx
There's "That's an easy mistake to make" and then there's "WTAF? On what planet where you on?"... This falls into the latter categoryThey can come back to us if their new provider is
idk but I know it wasnt me. Just annoys me that I have to waste my time sorting their incompetence.
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.