FOP2 - can't connect from CenturyLink

Dashrender

I have multiple users using CenturyLink for their ISP and they can't connect to my FOP2 server which is hosted in Chicago and I'm able to get to from Cox as an ISP just fine.

I get these:
https://i.imgur.com/pIiaXND.png

https://i.imgur.com/SQNBXeD.png

I am using the standard port 4445.
This is hosted on Vultr, with Cloudfare as the DNS with no proxy.

travisdh1

I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

JaredBusch

@Dashrender said in FOP2 - can't connect from CenturyLink:

I am using the standard port 4445.

............

FFS don't confuse things.....

You do not access FOP2 on a specific port.

You use https://pbx.domian.com/fop2

Yes, FOP2 itself uses port 4445 behind the scenes.

JaredBusch

@travisdh1 said in FOP2 - can't connect from CenturyLink:

I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

This is what you see when you connect to FOP2

Dashrender

@travisdh1 said in FOP2 - can't connect from CenturyLink:

I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

I can get to port 443 - my FreePBX page loads just fine.

Dashrender

@JaredBusch said in FOP2 - can't connect from CenturyLink:

@Dashrender said in FOP2 - can't connect from CenturyLink:

I am using the standard port 4445.

............

FFS don't confuse things.....

You do not access FOP2 on a specific port.

You use https://pbx.domian.com/fop2

Yes, FOP2 itself uses port 4445 behind the scenes.

Thanks, you're right, but I still have the issue.

JaredBusch

@Dashrender said in FOP2 - can't connect from CenturyLink:

@travisdh1 said in FOP2 - can't connect from CenturyLink:

I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

I can get to port 443 - my FreePBX page loads just fine.

Said above screenshot is connecting to your FOP2 instance.

That wasn't the point of my reply..

The way you bought in port 4445 implied that you and your users are connecting to https://pbx.domain.com:4445

scottalanmiller

@Dashrender said in FOP2 - can't connect from CenturyLink:

@travisdh1 said in FOP2 - can't connect from CenturyLink:

I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

I can get to port 443 - my FreePBX page loads just fine.

FOP2 should be on that port along with it.

scottalanmiller

Is it working when you connect from other locations?

Dashrender

@scottalanmiller said in FOP2 - can't connect from CenturyLink:

@Dashrender said in FOP2 - can't connect from CenturyLink:

@travisdh1 said in FOP2 - can't connect from CenturyLink:

I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

I can get to port 443 - my FreePBX page loads just fine.

FOP2 should be on that port along with it.

it is for me, and JB.
My users get to the page, but it does the count up loading thing, then never completes - hence the error screens at the top.

JaredBusch

@Dashrender said in FOP2 - can't connect from CenturyLink:

@scottalanmiller said in FOP2 - can't connect from CenturyLink:

@Dashrender said in FOP2 - can't connect from CenturyLink:

@travisdh1 said in FOP2 - can't connect from CenturyLink:

I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

I can get to port 443 - my FreePBX page loads just fine.

FOP2 should be on that port along with it.

it is for me, and JB.
My users get to the page, but it does the count up loading thing, then never completes - hence the error screens at the top.

It is for everyone.

Your users simply are not getting the log in box, which is connecting to port 4445

JaredBusch

Once you are logged in to FOP2, port 4445 is the only outbound port from the local PC.

Dashrender

OK - JB to the rescue again.

He saw I was marking my allowed IPs as Local - FreePBX doesn't know the 4445 service, so it's not allowed to be part of Local as far as the firewall is concerned.

So two options exist -

mark allowed IPs as Trusted, not Local
create a custom service under the firewall, and set it as a local service, then IPs marked as Local will get access.

Thanks @JaredBusch