We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

cannot view localhost:4001 site not found

  • 6 ответов
  • 8 имеют эту проблему
  • 2 просмотра
  • Последний ответ от Partisanpixel

more options

I recently stopped using Chrome because of development issues and started using Firefox Quantum (now up to 58). I'm using Local by Flywheel to develop WordPress sites on my laptop, with Browsersync that automatically updates web pages with new styles. Those styles are tracked to the proxy server, like localhost:4000. I can see the updates in Chrome but FF gives me the 'Hmm. We’re having trouble finding that site'

Any suggestions on how to fix this?

I recently stopped using Chrome because of development issues and started using Firefox Quantum (now up to 58). I'm using Local by Flywheel to develop WordPress sites on my laptop, with Browsersync that automatically updates web pages with new styles. Those styles are tracked to the proxy server, like localhost:4000. I can see the updates in Chrome but FF gives me the 'Hmm. We’re having trouble finding that site' Any suggestions on how to fix this?

Выбранное решение

For whatever this is worth, I was having a similar issue with getting Flywheel Local to play nice with Browsersync and Firefox. A cocktail of three things did the trick for me:

  • I changed my Flywheel Site Domain to themename.test (so in my particular case, that would be humescores.test) as I saw it mentioned elsewhere that the default .local or .dev where causing problems. Then I had to make sure that this matched the Browsersync proxy setting in my gulpfile.js
  • I had to change the Browsersync port number in my gulpfile.js from 8080 to the default Browsersync port which is 3000, so that it would match the next step
  • I had to use the http://localhost:4000 in my browser URL as you mentioned, except in my particular case it was 3000

I hope this is helpful for others who are having similar issues!

Прочитайте этот ответ в контексте 👍 1

Все ответы (6)

more options

Did you set any proxy server in FF? I doubt a change from FF57 to FF58 would cause just this problem.

more options

I think if Firefox were blocking port 4001 (or 4000) it would say so.

Does Firefox seem to understand the address? It might help to use

http://localhost:4001/

or https as the case may be.

Or if you have the page open in Chrome, try

menu > More tools > Add to desktop

and see whether it will launch in Firefox from there (assuming Firefox is your default browser).

more options

Can you open files from localhost in Firefox via the location/address bar?

Does http://127.0.0.1:4000 work?

more options

I'm not sure why this started working but both http://localhost:4000 and http://127.0.0.1:4000 now work. I cleared out cookies and changed a few security setings, so something in that did the trick. Thanks to everyone who responded. I so appreciate the help!!

more options

Выбранное решение

For whatever this is worth, I was having a similar issue with getting Flywheel Local to play nice with Browsersync and Firefox. A cocktail of three things did the trick for me:

  • I changed my Flywheel Site Domain to themename.test (so in my particular case, that would be humescores.test) as I saw it mentioned elsewhere that the default .local or .dev where causing problems. Then I had to make sure that this matched the Browsersync proxy setting in my gulpfile.js
  • I had to change the Browsersync port number in my gulpfile.js from 8080 to the default Browsersync port which is 3000, so that it would match the next step
  • I had to use the http://localhost:4000 in my browser URL as you mentioned, except in my particular case it was 3000

I hope this is helpful for others who are having similar issues!

more options

thank you @mpbryant!