Skip to main content
July 23, 2025
Question

Google Maps Component Plugin : 404 Not found error

  • July 23, 2025
  • 5 replies
  • 0 views

I implemented the Google Maps Component Plugin in the Dev and Test environments, and everything worked as expected. However, after deploying to Production, Google Maps is not functioning. Upon inspecting the browser console, I see the following error: Failed to load resource: the server responded with a status of 404 (Not Found) - Googlemap.svg. I’ve checked the server configuration, and it appears to be identical to the other environments. Any idea what could be causing this issue?"

5 replies

harshas2775
July 23, 2025

you can try re-deploying the plugin again in the Admin Console. If the same error comes up then its better to check with Appian support team and check on the server end. 

shubhama926776
July 23, 2025

The 404 error for googleMap.svg typically means the Google Maps plugin wasn't properly deployed to Production - the static assets are missing.
First, verify the plugin is installed in Admin Console and re-deploy it from your working Dev/Test environment.
If the plugin is definitely installed, check for Production-specific issues like incorrect Google Maps API key configuration, network/firewall restrictions, or domain restrictions on the API key. 

July 24, 2025

Hi [mention:9861aef97eb2483a8b76175d9eda1e37:e9ed411860ed4f2ba0265705b8793d05] , the plugin was definitely installed correctly (and I re-installed to ensure it was). I also dumped the contents of the zip for the google plug-in zip - the package included all the assets and the checksums matched the other environments. 

From an Appian platform perspective, is there any particular System Logs that may prove to be helpful in troubleshooting this matter? i.e. Watch the logs for the googleMap.svg load? You may be correct in your hunch that it is related to the network and firewall -- I am currently investigating that avenue.

Thank you for your support.

shubhama926776
July 24, 2025

Generally error shows in below logs
tomcat-stdOut.log - Shows servlet/resource loading errors
application-server.log - Web server request/response issues

Keep us posted about your findings