1912231 - no connection at all in MacOS 15.0 (Sequoia public beta)

Status: RESOLVED INCOMPLETE

(Core :: Networking, defect)

Description

[Thomas Born]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Safari/605.1.15

Steps to reproduce:

MacOS version 15.0 Beta (24A5309e)
my Firefox version is 130.0b2 (64-bit).
I downloaded the Firefox beta BECAUSE of the "bug"

Trying to get any connection fails

Actual results:

Since upgrading to public beta of MacOS Sequoia (15.0), I can get no more connections, whatsoever, not even to my FritzBox! router.

Have tried to find faulty preferences, couldn't find any.

Other browsers work well, as far as I can see.

Could be solved by Apple in the future, but not sure, so I'm posting this.

Expected results:

establish network connections (and get them)

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Ed Guloien [:edgul]]

Thanks for the report. Could you collect some http logs for us?
Go to about:logging select log to a file, start logging and reproduce the behaviour.
Http logs can contain sensitive info so you can email to [e-mail].

Thanks!

Comment 3

[Thomas Born]

Attachment: Logfile

(In reply to Ed Guloien [:edgul] from comment #2)
> Thanks for the report. Could you collect some [http logs](https://firefox-source-docs.mozilla.org/networking/http/logging.html) for us?
> Go to `about:logging` select `log to a file`, start logging and reproduce the behaviour.
> Http logs can contain sensitive info so you can email to [e-mail].
> 
> Thanks!

Hi,

this is the logging info you requested.
I tried to reach:

1.  My router [192.168.178.1]
2. mozilla.org
3. taz.de

They all failed


________start logfile:

Comment 4

[Thomas Born]

(In reply to Ed Guloien [:edgul] from comment #2)

Thanks for the report. Could you collect some http logs for us?
Go to about:logging select log to a file, start logging and reproduce the behaviour.
Http logs can contain sensitive info so you can email to [e-mail].

Thanks!

Hi,

this is the logging info you requested.
I tried to reach:

1. My router [192.168.178.1]
2. mozilla.org
3. taz.de

They all failed

I hope the log is appended.
(I'm not used to this…)

Comment 5

[Yanis Lagha]

Thanks for the report, i'm using macOS 15.0 Sequoia beta 24A5264n and this is working as expected
I've tried the actual nightly and the last Firefox update and i'm not able to reproduce this behaviour

Comment 6

[Ed Guloien [:edgul]]

Are you using DoH? If you disable it does that fix the issue?

Comment 7

[Ed Guloien [:edgul]]

Can you also try clearing the cache?

Comment 8

[Valentin Gosu [:valentin] (he/him)]

2024-08-09 07:07:37.861959 UTC - [Parent 1433: DNS Resolver #4]: E/nsHostResolver DNS lookup thread - lookup completed for host [taz.de]: failure: unknown host.
2024-08-09 07:07:37.861978 UTC - [Parent 1433: DNS Resolver #4]: D/nsHostResolver nsHostResolver::CompleteLookup taz.de 0 804B001E resolver=0 stillResolving=0
2024-08-09 07:07:37.861986 UTC - [Parent 1433: DNS Resolver #4]: D/nsHostResolver nsHostResolver record 1381c1f20 new gencnt
2024-08-09 07:07:37.861993 UTC - [Parent 1433: DNS Resolver #4]: D/nsHostResolver Caching host [taz.de] negative record for 60 seconds.
2024-08-09 07:07:37.862000 UTC - [Parent 1433: DNS Resolver #4]: D/nsHostResolver CompleteLookup: taz.de has NO address
2024-08-09 07:07:37.862008 UTC - [Parent 1433: DNS Resolver #4]: D/nsHostResolver nsHostResolver record 1381c1f20 calling back dns users status:804B001E

The logs show that getaddrinfo doesn't work for some reason.
Do you have some custom DNS settings on your machine?

Comment 9

[Valentin Gosu [:valentin] (he/him)]

Possibly relevant resource: https://www.reddit.com/r/MacOSBeta/comments/1ddcicp/macos_sequoia_beta_1_internet_issues_and_fixes/

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:kershaw, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Comment 11

[Thomas Born]

I finally found what was wrong. My firewall was set to forbid incoming connections.

Only thing I still don‘t understand is why the same configuration worked before the system update.