welcome[bot]
commented
2 years ago Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additiona round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
- "Priority" labels will show how urgent this is for the team.
- "Status" labels will show if this is ready to be worked on, blocked, or in progress.
- "Need" labels will indicate if additional input or analysis is required.
Finally, remember to use https://discuss.ipfs.tech if you just need general support.
TMoMoreau
After installing (IPFS-Desktop-0.23.0.dmg) and enabling it, from instantly to after a few minutes, some sites/web-pages won't respond properly in the web browser Firefox (with Adblock Plus, Ghostery, NoScript, uMatrix) at the same time Google Chrome (with uMatrix) fails the same sites - e.g.: https://da.wikipedia.org/wiki/InterPlanetary_File_System https://github.com/ipfs/ipfs-desktop/releases https://downdetector.com/ https://docs.sophos.com/esg/sixm-android/help/en-us/index.html
System: Updated MacOS 10.15.7 (19H2026). Hardware: MacBook Pro (15-inch, Mid 2012), 2,3 GHz Quad-Core Intel Core i7. RAM: 8 GB 1600 MHz DDR3. Installed Sophos Home Premium.
(I have also tried to restart the PC after installing IPFS-desktop - same problem)
When web-access failed the dns-reply was ok: $ nslookup ipfs-search.com Server: 10.xx.0.1 Address: 10.xx.0.1#53 Non-authoritative answer: Name: ipfs-search.com Address: 146.70.80.218 $
$ nslookup downdetector.com Server: 10.xx.0.1 Address: 10.xx.0.1#53 Non-authoritative answer: Name: downdetector.com Address: 104.18.1.148 Name: downdetector.com Address: 104.18.0.148 $
Ping was also ok while failed web-access:
$ ping ipfs-search.com PING ipfs-search.com (146.70.80.218): 56 data bytes 64 bytes from 146.70.80.218: icmp_seq=0 ttl=55 time=17.408 ms 64 bytes from 146.70.80.218: icmp_seq=1 ttl=55 time=11.200 ms ^C --- ipfs-search.com ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 11.200/14.304/17.408/3.104 ms $ ping downdetector.com PING downdetector.com (104.18.1.148): 56 data bytes 64 bytes from 104.18.1.148: icmp_seq=0 ttl=57 time=12.277 ms 64 bytes from 104.18.1.148: icmp_seq=1 ttl=57 time=11.097 ms ^C --- downdetector.com ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 11.097/11.687/12.277/0.590 ms $
Se attachments.
Firefox:
Google Chrome: