Originally posted by Test User
Hi just trying to activate a function addon and have uploaded a manifest and pasted js code following the gihub examples as well as the sample video. When I do the last step of clicking the Private Add-on Install URL link it doesnt open the permissions screen and throws a 500 server error
This page isn’t working
go.servicem8.com is currently unable to handle this request.
HTTP ERROR 500
Hi Test User,
We understand you’re experiencing a 500 server error when trying to activate your Node.js function add-on via the Private Add-on Install URL.
Based on our troubleshooting guide, here are some common causes and steps to resolve this issue:
1. Verify Developer Account Registration
Ensure you have a valid developer account registered at Developer Registration | ServiceM8. Wait for developer account approval before creating client-facing add-ons.
2. Check Manifest.json Configuration
Verify your manifest.json file is properly configured with required metadata such as name, version, icon, actions, and OAuth scopes. The manifest.json is a required configuration file defining an add-on’s metadata, the “actions” available to users, and OAuth scopes.
3. Validate Function Code
Ensure your Node.js function code follows the proper structure and returns responses as JSON with an “eventResponse” property set to valid HTML. Simple Functions support Node.js (JavaScript) with a maximum execution duration of 15 seconds per request and 128 MB maximum memory per request.
4. Environment Requirements
Confirm you’re using Node.js 14.x or higher for Lambda functions and testing with a Chrome or modern browser.
5. Clear Browser Cache
Try accessing the Private Add-on Install URL in an incognito/private browser window to rule out browser caching issues.
If these steps don’t resolve the issue, the error may be server-side. We recommend creating a support ticket with the following information:
- Your developer account email
- The add-on name/ID
- Complete manifest.json content
Our technical team can then investigate the server logs for your specific add-on activation attempt.
Thanks,
Cody
Thanks Cody, I just checked and its now working. I thought when the developer tab appears it means the developer account is now confirmed since that tab isn’t there originally and also there is no other way to know its been approved since no email/notification comes in. I’ve set up the dev registrations before and when the developer tab appears everything has always worked after that so this was a first.