Fix Uno WASM Deployment
Budget: $15 – $25 AUD
I have an Uno Platform WebAssembly app that runs fine locally but refuses to come alive once copied to my dedicated server. The build finishes without errors; the challenge begins when the published files reach the host. I need someone who understands Uno Platform, .NET WebAssembly, and typical server environments (IIS, Apache, or Nginx) to identify what I’m missing in the server-side setup and get the site serving correctly.
Current situation
• Static files and the .wasm assets are on a dedicated machine with full admin access.
• Requests either return 404s or serve the loader page indefinitely.
• I suspect MIME types, compression settings, or a missing runtime component, but I’d like a thorough check rather than guesswork.
What I expect from you
1. Diagnose the hosting server configuration and adjust it so the published Uno Platform WASM build loads in all modern browsers.
2. Explain any required changes (web.config, service worker tweaks, SSL redirects, folder structure, etc.) so I can reproduce the process on staging and future releases.
3. Provide a brief post-deployment test plan confirming that routing, navigation, and asset loading work once the fix is applied.
You will have remote access or a zipped copy of the published output—whichever you prefer—to work against. I’m ready to start as soon as you are and will be available to test changes in real time.
Current situation
• Static files and the .wasm assets are on a dedicated machine with full admin access.
• Requests either return 404s or serve the loader page indefinitely.
• I suspect MIME types, compression settings, or a missing runtime component, but I’d like a thorough check rather than guesswork.
What I expect from you
1. Diagnose the hosting server configuration and adjust it so the published Uno Platform WASM build loads in all modern browsers.
2. Explain any required changes (web.config, service worker tweaks, SSL redirects, folder structure, etc.) so I can reproduce the process on staging and future releases.
3. Provide a brief post-deployment test plan confirming that routing, navigation, and asset loading work once the fix is applied.
You will have remote access or a zipped copy of the published output—whichever you prefer—to work against. I’m ready to start as soon as you are and will be available to test changes in real time.