UNFmontreal / BookedScheduler

Repository for the last open source version of Booked Scheduler. Further development will be conducted on branches, namely "Bugfix", "Features", "plugins". Release candidates on "RC" and final releases on "Final".
GNU General Public License v3.0
0 stars 0 forks source link

Firefox: connection has timed out #1

Open SamGuay opened 2 years ago

SamGuay commented 2 years ago

To Reproduce

  1. Open Firefox with add-ons OR all add-ons turned off.
  2. Try to go to https://reservation.unf-montreal.ca/ or https://reservation.unf-montreal.ca/Web/schedule.php and wait for the page to load.

(Note: It does load and work on Chromium and Firefox Mobile.)

Actual behavior

After ~5 minutes of trying to load the page, Firefox results with a Problem loading page message and the page never appears (see screenshot)

Expected behavior

The page should load as expected.

Screenshots

image

System information

Operating system: Ubuntu 20.04
Browser: Firefox 93.0
Javascript enabled: Yes
Cookies enabled: Yes
Flash version: Not installed
Java version: Not installed
Websockets supported: Yes
WebGL supported: Yes
Language: en-CA
bpinsard commented 2 years ago

Thanks for the issue report. Does that happen only on CRIUGM network, on WIFI only? Is that the same for other website (eg. dicom.unf-montreal.ca ). We had some weird network behavior reported by other users.

SamGuay commented 2 years ago

Does that happen only on CRIUGM network, on WIFI only?

:red_circle: CRIUGM-usagers wifi :red_circle: wired network @ CRIUGM :green_circle: my own LTE network

Is that the same for other website (eg. dicom.unf-montreal.ca )

It seems to be doing the exact same thing with dicom.unf-montreal.ca, etc. Working on Chromium but not FF.

bpinsard commented 2 years ago

I think I found the culprit. Firefox uses an external DNS over https internally, which in that case return the external IP address, instead of the internal one. If you disable the last option, it works. image

bpinsard commented 2 years ago

It's because the CRIUGM firewall doesn't have hairpin NAT (or NAT loopback) which is a not-so-common option anyway, so external IP addresses are not accessible from the inside.

SamGuay commented 2 years ago

Oh wow, interesting! It now works like a charm with this option disabled!