Solved Question: Webclient internal URL

Status
Not open for further replies.

Dynux

Customer
Basic Certified
Joined
Aug 10, 2020
Messages
5
Reaction score
1
Hello guys,

we are using 3CX v16.0.622 with an FQDN .3cx.it and we wonder if we can use this FQDN for the webclient internal url ( the customer does not want the warning about the certificate ).

If i try to reach the webclient URL into the LAN via the FQDN https://name.3cx.it:5001/webclient i got ERR_CONNECTION_TIMED_OUT (can be this a routing problem?)

Into the LAN we resolve the FQDN with our static public IP and not with the LAN ip.

Are there some other info that could be useful to troubleshoot this issue?

Thank you very much.
 
this is a problem with your router
 
I forgot to add that this customer is using a Windows Domain, so it has his own internal DNS server that cannot add a zone for .3cx.it name (in theory) .
 
If you were able to setup split DNS so that using the URL resolves to the internal IP it should work fine.

Your firewall will most likely not allow you to access the FQDN internally because it points to the same public IP that your PCs sit behind (usually referred to as hairpin traffic).

Failing that, another option (not recommended) would be to modify ALL PCs accessing the FQDN and creating entries in their hosts file.
 
  • Like
Reactions: JohnS_3CX
Glad to hear!
 
Status
Not open for further replies.

Forum statistics

Threads
112,025
Messages
590,367
Members
164,976
Latest member
Roman Mazur