Issues setting up dev environment on windows (quickstart-react example)

Hi @dnesh!

We had a bug in our example apps but have since introduced a fix. This error should no longer come up. Could you let me know if this issue still persists for you?

Thanks!

Hi @alessandra,

Thanks for getting back to me.

What should I do then?
Delete everything and download anew from github?

Because I reran “npm install” just a few days ago…

Dan

Hi @alessandra ,

So I reinstalled everything - now I don’t get any error message, but I also don’t seem to get my URL…

Terminal output:

PS D:\\dnesh\\Documents\\Monday\\quickstart-react> npm start

monday-integration-quickstart-app@0.0.1 start
npm run stop && concurrently “npm run server” “npm run expose”

monday-integration-quickstart-app@0.0.1 stop
kill-port 8301 && kill-port 4049 && kill-port 4040

0 process was killed
0 process was killed
0 process was killed
[0]
[0] > monday-integration-quickstart-app@0.0.1 server
[0] > react-scripts start
[0]
[1]
[1] > monday-integration-quickstart-app@0.0.1 expose
[1] > mtunnel -p 8301
[1]
[1] [22:38:18.098] INFO: your url is: https://old-fashioned-centipede-27.tunnel.monday.app
[0] (node:16372) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: ‘onAfterSetupMiddleware’ option is deprecated. Please use the ‘setupMiddlewares’ option.
[0] (Use node --trace-deprecation ... to show where the warning was created)
[0] (node:16372) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: ‘onBeforeSetupMiddleware’ option is deprecated. Please use the ‘setupMiddlewares’ option.
[0] Starting the development server…
[0]
[0] Compiled successfully!
[0]
[0] You can now view monday-integration-quickstart-app in the browser.
[0]
[0] Local: http://localhost:8301
[0] On Your Network: http://192.168.68.118:8301
[0]
[0] Note that the development build is not optimized.
[0] To create a production build, use npm run build.
[0]
[0] webpack compiled successfully

Status page (http://localhost:8301/status):

Did I miss anything?
What can I find the ngrok URL?

Thanks!

Hi @dnesh,

We’re investigating this issue but we suspect it has to do with using a VPN when running the start commands. Could you confirm whether you’re using a VPN?

Thanks!

Hi @alessandra ,
Thanks for the update.

In the meantime, I was able to complete the exercise by pointing the app to the local host URL instead of the illusive ngrok .

Hello @dnesh!

Thank you for keeping us informed.

Just to check here, are you using a VPN?

Cheers,
Matias

Hi @Matias,

Nope, I was not using any VPN.

Dan

Thank you for the confirmation @dnesh!

It will help with our investigation 🙂

Hi @dnesh!

We’re in the process of moving from using ngrok to our new mondaytunnel, which is currently live. It looks like we missed the URL when you first shared your error with us! we’re working on fixing the output messages to make the URL more visible. You should be able to run the start command and see a URL in the output that ends in tunnel.monday.app.

Let us know if you run into any issues!

Hi @alessandra @Matias.Monday
I have a similar problem. I get a similar url like dnesh but when I paste the url in the custom url like it was said in the quickstart guide section, nothing comes up and after a bit i get a 504 gateway timeout. Do you know the reason for this? I new to this field so I dont have a clue what to do next.

Thanks,
Hyder

Hello @hyderhafiz!

Can you please send a screen recording to appsupport@monday.com so that our technical team can take a closer look?

Please include in the screen recording the steps you are taking, your script and the issue you are seeing.

Cheers,
Matias

Hello,
I am facing the same issue, any updates?

Hello @Islam.Shaheen,

In this case, you should check your environment (firewall, antivirus, VPN, etc.) since the issue is likely to be somewhere there.

If none of that works, please send an email to appsupport@monday.com so we can take a closer look from there.

Cheers,
Matias

Hello Matias,

I’m having the exact same error as Hyder and I am not using any firewall, vpn or antivirus (other than Windows Defender). Is ther any follow up or solution to Hyder’s issue? Thank you.

Hello there @vchan and welcome to the community!

We will need you to please send an email to appsupport@monday.com so we can take a look into your particular case.

Please send all the information you have. Screenshots and screen recordings are very welcomed.

See you over there!

Cheers,
Matias

It’s the Node version. Had the same issue, changed from v18 to v16 and connected with no problem.

Thank you @shawn for sharing your experience!

And welcome to the community 💪

So, from what I gather, a few of you are hitting snags with the Quickstart React example. Here’s a hack I stumbled upon that might help: make sure your npm is up-to-date and try running the setup commands in your terminal as an administrator. Sometimes, it’s those little permissions gremlins causing all the chaos!

Thank you @Avenewera for sharing and welcome to the community!

The error ERR_OSSL_EVP_UNSUPPORTED that you rae facing in error code that you are facing arises when an application needs to use an [encryption, decryption], signing or verification algorithm not supported or implemented by the version of OpenSSL being used. The different causes for the error to be occured are as follows:-

1. Unsupported Algorithm
2. Incorrect OpenSSL Version
3. Misconfigured OpenSSL Installation
4. Missing Libraries
5. Code Issues

Many different ways to fix the error you need to understand in detail which help in solving it. Hope it helps!