Hello guys!
Im trying to debug my code, but this error displayed and i dont know why, i research on google they told me to check my Rest API or fail when loading image source....
Please help me with this error.
Thank you alot!
Hello,
This error can come from a few scenarios, but from my understanding it’s not related to your API or image data. The debugger failing with a 404 means Service Studio couldn’t establish a communication channel with your environment. So first make sure you’re properly connected to your environment, not using some VPN that can cause the error, and that your module is running in the same environment you’re debugging. Also try restarting Service Studio or switching the browser in the debugger panel.
Adding to @Sherif El-Habibi answer:
In the company I work this is usually related to network connectivity, more specificallly to Proxy settings. Please check if you have any proxy settings that might impact the communication between you service studio on your machine and the server.
Best regards,
Miguel
Hello
Khoa Nguyen,
Here is two common reasons you are facing above issue. please check below points are usefull for you.
1. Wrong or missing breakpoints
If the debugger cannot map your breakpoints to server routes, it may throw 404.
Ensure breakpoints are on server actions, screens, or logic that actually executes.
Remove all breakpoints, republish, add them again.
2.Network restrictions block debugger communication
Debugging uses a WebSocket-like communication between Service Studio and the platform.
A firewall/proxy/VPN may block it, causing 404.
Disable VPN and try again
Allow ports 443 and HTTPS WebSocket connections
If on corporate network, try from a home network.
Best Regards,
Shubham
Hi Khoa,
Adding to Sherif’s answer: a 404 in the debugger usually means that Service Studio can’t reach the debugging endpoint in your environment (not that your REST API or images are wrong).
A few things you can check:
Correct environment URL Make sure you are logging into the right environment URL in Service Studio. Open the same URL in a browser and confirm that ServiceCenter loads (for example: https:///ServiceCenter/).
No proxy / load balancer rewriting the path If you access the environment through a reverse proxy or load balancer, ask your infra team to confirm that paths like /ServiceStudio and /ServiceCenter are not being blocked or rewritten. If they are, the debugger endpoint will return 404.
Try a different browser and restart Close the current debug session, restart Service Studio, and try a different browser in the debugger panel (Edge/Chrome). Sometimes cached sessions in the browser cause issues.
Check with your platform admin If everything above looks fine, ask your platform admin to check the front-end logs or open a case with OutSystems support; they can see if the debugger endpoint is returning 404 for your machine.
So, the problem is most likely connectivity/configuration between Service Studio and the environment, not your module code.
Best regards, Miguel