cd ui; npm i; cd ..
> meshery-ui@1.0.0 postinstall
> patch-package
patch-package 8.0.0
Applying patches...
No patch files found
> meshery-ui@1.0.0 prepare
> cd .. && husky install ui/.husky
husky - install command is DEPRECATED
up to date, audited 1221 packages in -12s
369 packages are looking for funding
run `npm fund` for details
6 vulnerabilities (2 moderate, 3 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
cd provider-ui; npm i; cd ..
up to date, audited 561 packages in 9s
147 packages are looking for funding
run `npm fund` for details
2 vulnerabilities (1 moderate, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
cd ui; npm run lint:fix && npm run build && npm run export; cd ..
> meshery-ui@1.0.0 lint:fix
> next lint --fix
✔ No ESLint warnings or errors
> meshery-ui@1.0.0 build
> npm run clean && cross-env next build
> meshery-ui@1.0.0 clean
> rm -rf .next,out
info - Linting and checking validity of types
info - Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://next
js.org/docs/messages/swc-disabled
info - `compiler` options in `next.config.js` will be ignored while using Babel https://nextjs.org/docs/me
ssages/ignored-compiler-options
info - Creating an optimized production build
info - Compiled successfully
Warning: You have opted-out of Automatic Static Optimization due to `getInitialProps` in `pages/_app`. This
does not opt-out pages with `getStaticProps`
Read more: https://nextjs.org/docs/messages/opt-out-auto-static-optimization
info - Collecting page data
Route (pages) Size First Load JS
┌ λ / 103 kB 2.81 MB
├ /_app 0 B 2.57 MB
├ λ /404 1.33 kB 2.57 MB
├ λ /api/__coverage__ 0 B 2.57 MB
├ λ /configuration/catalog 1.25 kB 2.75 MB
├ λ /configuration/designs 957 B 2.75 MB
├ λ /configuration/designs/configurator 2.05 kB 2.59 MB
├ λ /configuration/filters 27.2 kB 2.64 MB
├ λ /extension/[...component] 10.9 kB 2.99 MB
├ └ css/f954b4d908952ed7.css 5.97 kB
├ λ /extension/AccessMesheryModal 220 B 2.57 MB
├ λ /extensions 10.3 kB 2.58 MB
├ λ /management/adapter 30.8 kB 2.82 MB
├ λ /management/connections 31.9 kB 2.6 MB
├ λ /management/environments 969 B 2.62 MB
├ λ /management/workspaces 966 B 2.62 MB
├ λ /performance 9.2 kB 2.86 MB
├ └ css/c7f80fc49a0d3e7c.css 2.5 kB
├ λ /performance/profiles 34 kB 2.89 MB
├ λ /settings 114 kB 2.9 MB
└ λ /user/preferences 15.9 kB 2.58 MB
+ First Load JS shared by all 2.57 MB
├ chunks/framework-c3d82864605bdcec.js 46.6 kB
├ chunks/main-b4581ec43d6d814d.js 29.7 kB
├ chunks/pages/_app-ad63c14a850a6c5a.js 2.49 MB
├ chunks/webpack-6af17706e194af28.js 1.99 kB
└ css/6d9af26d2f83a2e6.css 6.03 kB
λ (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps)
> meshery-ui@1.0.0 export
> next export
info - using build directory: /mnt/e/Projects/meshery/ui/.next
info - Copying "static build" directory
info - Launching 3 workers
warn - Statically exporting a Next.js application via `next export` disables API routes.
This command is meant for static-only hosts, and is not necessary to make your application static.
Pages in your application without server-side data dependencies will be automatically statically exported b
y `next build`, including pages powered by `getStaticProps`.
Learn more: https://nextjs.org/docs/messages/api-routes-static-export
info - Copying "public" directory
info - Exporting (17/17)
Export successful. Files written to /mnt/e/Projects/meshery/ui/out
cd provider-ui; npm run lint:fix && npm run build && npm run export; cd ..
> provider-ui@1.0.0 lint:fix
> next lint --fix
✔ No ESLint warnings or errors
> provider-ui@1.0.0 build
> npm run clean && next build
> provider-ui@1.0.0 clean
> rm -rf .next,out
Skipping linting
✓ Checking validity of types
Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.or
g/docs/messages/swc-disabled
✓ Creating an optimized production build
✓ Compiled successfully
Static worker unexpectedly exited with code: null and signal: SIGTERM
Static worker unexpectedly exited with code: null and signal: SIGTERM
Static worker unexpectedly exited with code: null and signal: SIGTERM
⚠ Restarted collecting page data for undefined because it took more than 60 seconds
⚠ See more info here https://nextjs.org/docs/messages/static-page-generation-timeout
⚠ Restarted collecting page data for undefined because it took more than 60 seconds
⚠ Restarted collecting page data for undefined because it took more than 60 seconds
⚠ Restarted collecting page data for undefined because it took more than 60 seconds
⚠ Restarted collecting page data for undefined because it took more than 60 seconds
Static worker unexpectedly exited with code: null and signal: SIGTERM
Static worker unexpectedly exited with code: null and signal: SIGTERM
Static worker unexpectedly exited with code: null and signal: SIGTERM
> Build error occurred
Error: Collecting page data for undefined is still timing out after 2 attempts. See more info here https://
nextjs.org/docs/messages/page-data-collection-timeout
at onRestart (/mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/build/index.js:744:39)
at Worker.isPageStatic (/mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/lib/worker.js:95:40)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Span.traceAsyncFn (/mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/trace/trace.js:1
05:20)
at async /mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/build/index.js:928:56
at async Span.traceAsyncFn (/mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/trace/trace.js:1
05:20)
at async Promise.all (index 6)
at async /mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/build/index.js:862:17
at async Span.traceAsyncFn (/mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/trace/trace.js:1
05:20)
at async /mnt/e/Projects/meshery/provider-ui/node_modules/next/dist/build/index.js:801:124
Collecting page data .root@DESKTOP-RKT0J2E:/mnt/e/Projects/meshery# ```@Arti_Gaund, please enclose the entirety of your terminal output in a
code wrapper
and use [details=Summary]This text will be hidden[/details] to hide the long output/logs.
Also, include a description of the issue (the situation and your environment details). You have neglected to include your node and npm versions as requested.
Oh, you did, but you buried those details in the same code wrapper as your copy/paste. The lack of attention to formatting and care given to describing your issue makes it a challenge to support you.
HI @Arti_Gaund Make sure to follow the guide here Setting up Meshery Development Environment on Windows | Meshery
I had followed all the steps according to documentation. I have installed all make, go, gcc, node. I am using wsl2. But still getting the same error.
Hi @Arti_Gaund
Idk what your error is but I believe I can help you out.
I was facing a lot of issues trying to setup meshery locally on windows system. Below is what worked for me after troubleshooting and going through various blogs.
Setting Up Meshery
- docker desktop should be on
- open the meshery codebase in WSL (ubuntu)
( this means directly git clone the repo in the WSL , not in windows command prompt.) - install docker and minikube and kubectl in WSL
After you are done with this,
RUN:
minikube start
curl -L https://meshery.io/install | PLATFORM=docker bash -
Hope this works out for you 
Let me know if you are facing any issues using this.
Thanks. I will try these steps today.
Hi, i have to follow the above steps after cloning the rep though wsl ? According to documentation after cloning we have to run make ui-setup command in wsl to install all the dependencies of ui, i was following that.
😄 minikube v1.35.0 on Ubuntu 24.04 (amd64)
E0331 21:21:43.657619 1335 start.go:812] api.Load failed for minikube: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
✨ Using the docker driver based on existing profile
🛑 The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force.
💡 If you are running minikube within a VM, consider using --driver=none:
📘 https://minikube.sigs.k8s.io/docs/reference/drivers/none/
💡 Tip: To remove this root owned cluster, run: sudo minikube delete
❌ Exiting due to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.``` I am getting following error in minikube startResolved the error. Followed the following discussion Getting a 404 Error After Setting Up Meshery for the First Time? Here Is How I Solved It
2 Likes
This is good news! 
Hi @Arti_Gaund, That is good news. Can you please mark your chat as the solution?
The discussion I have followed, the solution it has to remove node_module of both ui and provider-ui folder, because may be it got corrupted, I did that , so I used the following commands :
cd ui
rm -rf node_modules
npm install
cd …
cd provider-ui
rm -rf node_modules
npm install
cd …
When I again used the command:
make ui-build
It was still showing the error:
“Restarted collecting page data for undefined because it took more than 60 seconds”
but its an nextjs error, as project is big, so its taking lots of time to collect all the page data, so it was exceeding the time limit of 60 sec (which was by default). So I have increase the timeout limit by adding staticPageGenerationTimeout: 2000 (I used 600 also but it didn’t work) in nextconfig file of both ui and provider-ui folder.
I have followed the instructions for contributing to the Meshery UI:
- Cloned the Meshery repository
- Ran the following commands:
- make ui-setup
- make ui-build
- make ui-server
However, Meshery is not running locally as expected. After completing the above steps, I tried accessing https://localhost:9081 in my browser. It opens a page where I have to select a provider (the available options are “Meshery” or “None”). After selecting a provider, I encounter a 404 Not Found error.
Here is the error shown in the terminal:
INFO[2025-04-21T06:48:24Z] attempting to save connection meshery to remote provider with status connected app=meshery
ERRO[2025-04-21T06:48:24Z] Status Code: 500 .failed to save the connection “” of type “meshery” with status “connected” app=meshery code=meshery-server-1345 probable-cause= severity=2 short-description=“Unable to save Meshery connection” suggested-remediation=
Could you please help me troubleshoot this issue or let me know if I missed any steps?
