Problem showing website in the browser

This is the error message that I’m getting

Error: pkg-config: no bottle available!
You can try to install from source with:
brew install --build-from-source pkg-config
Please note building from source is unsupported. You will encounter build
failures with some formulae. If you experience any issues please create pull
requests instead of asking for help on Homebrew's GitHub, Twitter or any other
official channels.

Please explain in more details where and when are you getting this error exactly?

Thanks Toedor

I’m running Wappler on my Mac and trying to use my own server local host instead of something like Mamp. So I can add extentions like the youtube-player.

When I switched from default Wappler server to local host - I then could not see the preview of my website pages in the browser. That was the error I was getting. Thanks

It’s a Node JS website I also keep getting asked to install Node packages and when done so it asks repeatedly and I have to tick NO as an option.

Also when I run the Web Server it says Library not allowed and something to do with brotli/lib/libbrotlienc.1.dylib

Hi Brett,

Try creating a new NodeJS project, making sure that you set it to use your own server. If that works, maybe Brotli will be installed by Wappler. Being on a Windows platform, I never see any Brotli prompts, so I suspect that this is an iOS issue.

If the new project works, try running your current project, maybe the issue is fixed. If not, Google Brotli install and use those directions to install Brotli on your system.

Hopefully that will solve the problem.

So if i understand correctly - you have an actual local server running nodejs, and you did not simply switch from "Wappler Local Server" to "Own Server" in the target options?

yes I switched it and guess that caused the problem - couldn;t switch back, I’ll make a new one like Ben said

Cheers

Hi Brett,

It’s possible that the version of Node.js installed on your Mac is outdated and not fully compatible with Wappler. Installing the latest Node.js v24 LTS release on your Mac may resolve the problem.

1 Like

Thanks so much Gupast, that was the solution ans all working on my 2018 intel Mac!

2 Likes