Running into hiccups? Don’t worry — we’ve got your back. Below are the most common issues developers face during the hackathon, along with quick fixes to get you back on track.
“It worked at home but not here.”
Development environments can behave differently depending on corporate policies, VPNs, proxies, or firewalls.
Are you behind a corporate firewall or proxy ?
Try switching to a personal/hotspot connection to test if your access is being blocked.
Try accessing the following tools:
If these are inaccessible, contact your network admin or try using a VPN.
Disable strict antivirus/endpoint security tools temporarily during development.
You have an Alkamist — work with them to see what might be the issue.
Make sure you followed all steps on the Merlin install guide .
Confirm that Merlin is installed and accessible from your terminal or command prompt.
If Merlin is not installing or starting, verify your machine meets the minimum requirements:
Memory: At least 8GB RAM recommended.
CPU: Minimum 4 cores recommended.
Check your machine permissions and policies — some corporate or personal settings may block software installation or network calls. If unsure, contact your IT or try on a different machine.
Refer to the detailed Merlin Troubleshooting guide for common install issues.
Make sure your SDK version is up to date. Use merlin upgrade
if you have Merlin installed.
You have an Alkamist — work with them to help identify any environment-specific blockers.
If your API calls are failing or you’re getting authentication or connectivity errors, here are the most common things to check:
Confirm your API key is active and correctly copied.
Verify you are sending the API key correctly, usually in the Authorization
header as Bearer <your_api_key>
.
Use Postman to test your API calls and verify the requests and responses.
Check your network and firewall settings — corporate policies or VPNs may block outgoing requests.
Make sure your machine’s date and time are accurate — time skew can cause authentication failures.
Look out for rate limits or throttling errors (usually HTTP 429). If you hit rate limits, slow down your requests or wait before retrying.
Review the response error messages carefully; they often contain clues about what went wrong.
You have an Alkamist — work with them to troubleshoot API access or key issues.
Tip: If you receive unexpected errors, double-check your API key is entered correctly and that your account has the necessary permissions.
Sometimes it’s not you — it’s the setup. Here’s a checklist of other common “gotchas”:
✅ You’ve restarted your development server after installing dependencies
✅ You’ve cleared your browser cache
✅ You’re not using a restricted guest WiFi network
✅ You’re running Node.js LTS (≥ v18 recommended)
✅ You’ve updated to the latest SDK or tooling versions
🧠 Developer Docs Everything you need to get going with SDK, APIs, and deployment. 💻 GitHub Repo Star, fork, or raise issues directly in the Hackathon repo.
Every developer hits snags — especially in a high-energy hackathon. Take a breath, ask questions, and keep building.
You’ve got this. 🚀