Network error while checking update for Mulch #679
Comments
|
Mulch is discontinued in December 2024 |
|
Stacktrace: Logs: Device information:
|
Ow, why? I only used it because last update of cromite gives error of all https being not safe, so untill that is fixed i used mulch, now I switch between duckduckgo and firefox fusion |
Hmm.. As for Mulch (and Mull), the dev stopped the project due to financial crisis. |
You seem to know alot of background information as in being pretty involved in the know how, what would you suggest as a good fork? Cause those were kinda my three used forks... I read ironfist could be a mull replacement, but it is pretty new... And I read that firefox and it's forks lack something that on desktop is easy to change, but can't be done on android and is kinda big security risk, forgot what it was... |
|
With my little knowledge and understanding, I can say Ironfox is totally dependable. FF-updater dev considering to include here. IF going to be more user-friendly than Mull. In case of chromium forks, you have to stay with Brave. This is technically most robust, has large dev team, solid revenue model. But the company behind Brave is not trustworthy, has history of malpractices. We don't know if they do such again. If you are not comfortable with the hardening procedure of Brave, and don't need the fingerprint mitigations much, then use Vivaldi. Though not fully open source, Vivaldi has great privacy policy, privacy-friendly jurisdiction (out of 14 eyes) and long history of transparency. The plan is - main Browser will be FF fork, secondary Chromium fork and third one is only for banking, logged in sites where NO browsing will be done. Enjoy 😊 |
|
Important first questions
Is your FFUpdater up-to-date? If not, please abort and update FFUpdater.
Do you spot similar issues in https://github.com/Tobi823/ffupdater/issues? If yes, please abort and add your error message as a comment to the existing issue.
Describe the bug
Network error while checking update for Mulch
Error message from FFUpdater
Please copy and paste the error message with the stacktrace and error log here:
at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:128)
at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:295)
at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:207)
at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
Caused by: android.system.ErrnoException: isConnected failed: ETIMEDOUT (Connection timed out)
at libcore.io.IoBridge.isConnected(IoBridge.java:334)
... 28 more
`
Device information:
The text was updated successfully, but these errors were encountered: