| View previous topic :: View next topic |
| Author |
Message |
ecko
Tux's lil' helper
Joined: 04 Jul 2010
Posts: 99
|
 Posted: Sat Dec 25, 2021 12:05 am Post subject: [solved] monit: firefox cannot open localhost:2812 |
 |
|
I use app-admin/monit-5.29.0 but I cannot open the admin page http://localhost:2812/ in firefox. The page opens well in links, dillo, palemoon. The error in firefox / firefox-bin is "The connection to the server was reset while the page was loading." I thought I forgot to enable HTTP in the settings, but I checked and I have "Don’t enable HTTPS-Only Mode" in Settings/Privacy. There are a lot of settings related to HTTPS in about:config, all of them are at their default value.
The monit page also does not open in ungooged-chromium with a clear error ("This site can’t provide a secure connection - localhost sent an invalid response - ERR_SSL_PROTOCOL_ERROR") which at least is clear. However, the CUPS admin page http://localhost:631/ is also HTTP-only and can be opened without trouble on all my browsers.
So why does firefox not open localhost:2812 if it can open localhost:631? Does it have to do with the port > 1024?
Last edited by ecko on Wed Jan 05, 2022 10:36 pm; edited 1 time in total |
|
| Back to top |
|
 |
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1655
|
|
| Back to top |
|
|
ecko
Tux's lil' helper
Joined: 04 Jul 2010
Posts: 99
|
| Posted: Sun Jan 02, 2022 3:36 pm Post subject: |
|
|
I left everything to the system defaults: USE="ipv6 pam ssl".
/etc/monitrc:
| Code: |
set httpd port 2812 and
use address localhost # only accept connection from localhost (drop if you use M/Monit)
allow localhost # allow localhost to connect to the server and
allow admin:monit # require user 'admin' with password 'monit'
with ssl { # enable SSL/TLS and set path to server certificate
# pemfile: /etc/ssl/certs/monit.pem
}
set ssl {
verify : enable, # verify SSL certificates (disabled by default but STRONGLY RECOMMENDED)
selfsigned : allow # allow self signed SSL certificates (reject by default)
}
|
I now tried with USE="-ssl" and retested all browsers (dillo, links, palemoon, ungoogled-chromium, firefox, firefox-bin), same results (works will every browser except recent firefox/firefox-bin).
I bissected with mozreg (this thing is great!)
Assumed FF24 works because palemoon was forked from that.
| Code: |
pip3 install --user mozregression
cd ~/.local/bin
MOZ_DISABLE_CONTENT_SANDBOX=1 ./mozregression --good 24
|
It narrows the problem between 2020-10-26 and 2020-10-27.
| Code: |
2:56.39 INFO: Using local file: /tmp/tmp09joyo6c/2020-10-24--mozilla-central--firefox-84.0a1.en-US.linux-x86_64.tar.bz2 (downloaded in background)
2:56.39 INFO: Running mozilla-central build for 2020-10-24
3:03.91 INFO: Launching /tmp/tmp64isnqdh/firefox/firefox
3:03.91 INFO: Application command: /tmp/tmp64isnqdh/firefox/firefox -profile /tmp/tmpqsza35gt.mozrunner
3:03.92 INFO: application_buildid: 20201024213340
3:03.92 INFO: application_changeset: 2df411f957801f07a8089a04c907bda66c69ec13
3:03.92 INFO: application_name: Firefox
3:03.92 INFO: application_repository: https://hg.mozilla.org/mozilla-central
3:03.92 INFO: application_version: 84.0a1
Was this nightly build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', 'back' or 'exit' and press Enter): good
3:12.80 INFO: Narrowed nightly regression window from [2020-10-21, 2020-10-27] (6 days) to [2020-10-24, 2020-10-27] (3 days) (~1 steps left)
3:12.80 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2df411f957801f07a8089a04c907bda66c69ec13&tochange=ab66bd46c2d6874336d5fad4faceaa9b9448ff5f
3:12.80 INFO: Using local file: /tmp/tmp09joyo6c/2020-10-26--mozilla-central--firefox-84.0a1.en-US.linux-x86_64.tar.bz2 (downloaded in background)
3:12.80 INFO: Running mozilla-central build for 2020-10-26
3:20.06 INFO: Launching /tmp/tmp2eskxqv5/firefox/firefox
3:20.06 INFO: Application command: /tmp/tmp2eskxqv5/firefox/firefox -profile /tmp/tmpalg091t1.mozrunner
3:20.06 INFO: application_buildid: 20201026092834
3:20.06 INFO: application_changeset: b1a74943bc51bd3e62ea52242ec5e403ea3760bb
3:20.06 INFO: application_name: Firefox
3:20.06 INFO: application_repository: https://hg.mozilla.org/mozilla-central
3:20.06 INFO: application_version: 84.0a1
Was this nightly build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', 'back' or 'exit' and press Enter): good
3:31.96 INFO: Narrowed nightly regression window from [2020-10-24, 2020-10-27] (3 days) to [2020-10-26, 2020-10-27] (1 days) (~0 steps left)
3:31.96 INFO: Got as far as we can go bisecting nightlies...
3:31.96 INFO: Last good revision: b1a74943bc51bd3e62ea52242ec5e403ea3760bb (2020-10-26)
3:31.96 INFO: First bad revision: ab66bd46c2d6874336d5fad4faceaa9b9448ff5f (2020-10-27)
3:31.96 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b1a74943bc51bd3e62ea52242ec5e403ea3760bb&tochange=ab66bd46c2d6874336d5fad4faceaa9b9448ff5f
3:31.96 INFO: Switching bisection method to taskcluster
3:31.96 INFO: Getting mozilla-central builds between b1a74943bc51bd3e62ea52242ec5e403ea3760bb and ab66bd46c2d6874336d5fad4faceaa9b9448ff5f
3:34.37 WARNING: Skipping build ab66bd46c2d6: Unable to find build info using the taskcluster route 'gecko.v2.mozilla-central.shippable.revision.ab66bd46c2d6874336d5fad4faceaa9b9448ff5f.firefox.linux64-opt'
[...]
3:41.86 CRITICAL: First build b1a74943bc51 is missing, but mozregression can't find a build before - so it is excluded, but it could contain the regression!
3:43.36 WARNING: Skipping build d54d820d6a8d: Unable to find build info using the taskcluster route 'gecko.v2.mozilla-central.shippable.revision.d54d820d6a8d24a86d6e03d976280182cbd7758d.firefox.linux64-opt'
[...]
3:50.15 CRITICAL: Last build ab66bd46c2d6 is missing, but mozregression can't find a build after - so it is excluded, but it could contain the regression!
[...]
3:51.29 INFO: There are no build artifacts for these changesets (they are probably too old).
|
It cannot bissect further this way because they do not keep the binaries of each commit for so long. The problem could be any of the following 300+ commits:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b1a74943bc51bd3e62ea52242ec5e403ea3760bb&tochange=ab66bd46c2d6874336d5fad4faceaa9b9448ff5f |
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1655
|
|
| Back to top |
|
|
ecko
Tux's lil' helper
Joined: 04 Jul 2010
Posts: 99
|
| Posted: Sun Jan 02, 2022 9:01 pm Post subject: |
|
|
| turtles wrote: |
Nice work.
That is some impressive debugging.
|
Indeed the Mozilla guys made an awesome work with mozregression. Just launch in the terminal, it opens successively different FF versions, you just have to type "good " or "bad" on the terminal for each and after 3 minutes of iterations it tells which commit caused the problem.
Thanks, release notes seem related. Since cups and syncthing managed to have it working, I guess the problem is monit, not firefox. I'll have to report upstream. |
|
| Back to top |
|
|
ecko
Tux's lil' helper
Joined: 04 Jul 2010
Posts: 99
|
|
| Back to top |
|
|
turtles
Veteran
Joined: 31 Dec 2004
Posts: 1655
|
| Posted: Thu Jan 06, 2022 12:35 am Post subject: |
|
|
Ahhh there you go, I was going to suggest that but then you had other stuff working on localhost.
Glad its working
_________________
Donate to Gentoo |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
