localhost:3000 not responding about flynt

[steffenbew]

Hi Michael, happy to hear you're giving Flynt a try!
Did you follow step 2 of the install guide and adjust the host variable to match your local url?
Change the host variable in flynt/build-config.js to match your host URL: const host = 'your-project.test'

[MichaTausKamR]

Thanks for the fast response! Yes, I changed it to localhost. When I do netstat, I can see that node.exe listens on port 3000.Am 04.12.2019 17:23 schrieb Steffen Bewersdorff <[email protected]>:Hi Michael, happy to hear you're giving Flynt a try! Did you follow step 2 of the install guide and adjust the host variable to match your local url? Change the host variable in flynt/build-config.js to match your host URL: const host = 'your-project.test' —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[domtra]

Hi Michael,
so your actual WordPress installation is accessible via http://localhost? Then it should be const host = 'localhost'. If you did set up a VirtualHost under some other domain, please adjust the host variable accordingly.
It could also be, that a browersync setting is preventing localhost:3000 from working correctly. Please try setting https to false in build-config.js under browserSync. https://github.com/flyntwp/flynt/blob/master/build-config.js#L51

Hope this helps.

[MichaTausKamR]

Hello domtra, yes my WordPress runs on http://localhost. I tried that again and could even work with phpmyadmin in xampp.

Anyway, I tried your changes and it did something. Instead of giving me the error instantly, it now waits about a minute and then throws up an error "Firefox can't establish a connection to localhost."

:(

I only have Windows Defender and the Windows Firewall as security.

Regards

[domtra]

that is indeed strange.

i can only think of the firewall blocking node.exe from accessing port 80 on localhost. maybe you can explicitly allow that somehow.

[areddxx]

I was having this issue as well, tried setting https to false and it worked for me.

May be worth adding to the readme.