Toggle sidebar Toggle sidebar

Solved 3CX | [Action Required] Change of FQDN Endpoint

Status
Not open for further replies.
cactus

cactus

Free User
Joined
Oct 17, 2014
Messages
11
Reaction score
1
You write:
Review your network access rules and ensure that you allow connectivity to activate.3cx.com.
Click to expand...
But how to verify this? Port 80 doesn't respond, but Ping does:

Pinging activate.3cx.com [172.67.39.236] with 32 bytes of data: Reply from 172.67.39.236: bytes=32 time=26ms TTL=57

Anything else to check, please?
 
cactus said:
You write:

But how to verify this? Port 80 doesn't respond, but Ping does:

Pinging activate.3cx.com [172.67.39.236] with 32 bytes of data: Reply from 172.67.39.236: bytes=32 time=26ms TTL=57

Anything else to check, please?
Click to expand...
This uses port 443.
 
  • Like
Reactions: cactus
Ŷou are will be fine, as you get a ping response from activate.3cx.com and not blocking outbound ports

Some companies will lock down 3cx access to the internet, so they need to allow access activate.3cx.com
 
  • Like
Reactions: cactus
That's what I imagined, but the message posted is a bit muddy.

I can open http://activate.com:443 and receive a "400 Bad Request", as with telnet:

telnet activate.3cx.com 443 HTTP/1.1 400 Bad Request Server: cloudflare Date: Sat, 20 Nov 2021 14:58:55 GMT Content-Type: text/html Content-Length: 155 Connection: close CF-RAY: - <html> <head><title>400 Bad Request</title></head> <body> <center><h1>400 Bad Request</h1></center> <hr><center>cloudflare</center> </body> </html>

That should settle it. Thank you.

PS: How do I mark this as solved?
 
cactus said:
That's what I imagined, but the message posted is a bit muddy.

I can open http://activate.com:443 and receive a "400 Bad Request", as with telnet:

telnet activate.3cx.com 443 HTTP/1.1 400 Bad Request Server: cloudflare Date: Sat, 20 Nov 2021 14:58:55 GMT Content-Type: text/html Content-Length: 155 Connection: close CF-RAY: - <html> <head><title>400 Bad Request</title></head> <body> <center><h1>400 Bad Request</h1></center> <hr><center>cloudflare</center> </body> </html>

That should settle it. Thank you.

PS: How do I mark this as solved?
Click to expand...
Usually you don't start pinging 3CX services for no reason. The FQDN will change that's all you need to know. "Validating" it is not your job.
 
Please, read my question again. 3CX write me to:
Review your network access rules and ensure that you allow connectivity to activate.3cx.com.
Click to expand...
So, I'm asking what steps to take to validate that connection, and I don't start pinging 3CX services for no reason.
 
cactus said:
Please, read my question again. 3CX write me to:

So, I'm asking what steps to take to validate that connection, and I don't start pinging 3CX services for no reason.
Click to expand...
To validate the connection, ping might not work. Many services are ICMP-blocked for obvious security reasons.

Did it work for you? The bad request page doesn't really matter, it does mean that connection worked tho. So if you do filter, filter by URL.
 
Sorry, I don't understand your question.
As I wrote above, I can telnet that URL on port 443.
We don't do URL filtering, so I assume the test confirms, that connection is possible.
 
cactus said:
Sorry, I don't understand your question.
As I wrote above, I can telnet that URL on port 443.
We don't do URL filtering, so I assume the test confirms, that connection is possible.
Click to expand...
If you don't filter anything, you don't need to worry about that at all. It will work.

What they mean in the post is if you use URL filtering or IP whitelisting. In that case, you would need to adjust settings to allow the connection to work.
 
Thank you. That was my assumption, but the message from 3CX wasn't very clear.
 
  • Like
Reactions: Evolute IT
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom