
Completed
Posted
Paid on delivery
We are looking for a developer specializing in EvolutionsGO (WhatsApp API in Go) and Supabase to urgently resolve a critical issue in QR Code generation in our healthcare SaaS system. The system currently uses EvolutionsGO to mirror and connect customers' WhatsApp, with the infrastructure running on Easypanel (Ubuntu Server / Traefik / Cloudflare Gray Cloud). Recently, the system stopped generating the QR Code on the SaaS screen for new connections, although the local databases (PostgreSQL and Redis) dedicated to the API are active and operating on Easypanel. The selected professional will be responsible for: 1. Analyzing EvolutionsGO logs in Easypanel to identify the cause of the failure in the connection route (/instance/connect or similar) that prevents the generation of the QR Code payload. 2. Clean up possible crashed/corrupted sessions or instances in local databases (Redis/Postgres). 3. Validate whether the current version of EvolutionsGO installed requires a compatibility update with the WhatsApp library (Baileys/Go). 4. Reestablish the complete connection flow, from clicking the SaaS button, through the call via Edge Function, to the successful generation of the QR Code and the status change to 'connected'. We offer full access to GitHub (source code), Easypanel (server) and Supabase (database). It is essential to have practical and direct experience with EvolutionsGO for this urgent fix.
Project ID: 40789240
177 proposals
Remote project
Active 6 days ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
177 freelancers are bidding on average $135 USD for this job

I can get your QR code generation working again in EvolutionGO, from the Supabase Edge Function call through to the "connected" status. I'll start with the EvolutionGO container logs in Easypanel and trace the /instance/connect request to see where the QR payload stops. The usual causes are a stale or corrupted whatsmeow device session in Postgres or Redis, an outdated whatsmeow version that WhatsApp's protocol changes have broken, or a webhook or Traefik routing issue. Once I've cleared the broken instances, updated the library if needed and checked the Edge Function and the webhook that updates the status, I'll test a real connection from start to finish. I can start immediately once I have access.
$30 USD in 1 day
7.6
7.6

Hi, I can help diagnose and resolve the WhatsApp QR Code generation issue in your healthcare SaaS without disrupting existing connections. With 10+ years of development experience, I can troubleshoot API integrations, Supabase, PostgreSQL, Redis, and server infrastructure. My approach: - Review EvolutionsGO logs in Easypanel. - Debug the /instance/connect endpoint and Supabase Edge Function. - Check Redis/PostgreSQL sessions and safely repair corrupted instances. - Investigate EvolutionsGO and WhatsApp library compatibility. - Verify Traefik, Cloudflare, and API connectivity. - Test the complete QR generation and WhatsApp connection flow. I'll back up relevant data before making changes and provide a clear explanation of the root cause and fixes. I can start immediately and prioritize restoring the connection flow. Muhammad Rizwan LA
$50 USD in 2 days
7.1
7.1

Hi there, I understand the urgency of resolving the QR Code generation issue in your healthcare SaaS system utilizing EvolutionsGO and Supabase. With extensive experience in working with WhatsApp APIs and cloud solutions, I'm confident in addressing the challenges you're facing. My approach will begin with a thorough analysis of the EvolutionsGO logs within Easypanel to pinpoint the connection route failure causing the QR Code generation problem. I will also examine the PostgreSQL and Redis databases for any crashed or corrupted sessions and ensure they are cleaned up. Understanding the importance of compatibility, I will verify whether the installed version of EvolutionsGO requires an update with the WhatsApp library (Baileys/Go) and proceed accordingly. Restoring the connection flow is a priority, and I will ensure that it functions seamlessly from the initiation on your SaaS platform through to successful QR Code generation and status update to 'connected'. My familiarity with the infrastructure involving Ubuntu Server, Traefik, and Cloudflare will facilitate a swift and effective resolution. I am committed to delivering a solution that ensures stable and efficient operation, and I appreciate the opportunity to contribute my skills to this critical task. Best Regards
$30 USD in 5 days
6.6
6.6

EvolutionsGO instances failing during QR code generation on Easypanel usually stem from either stale session locks in Redis after an ungraceful disconnect, or an outdated WhatsApp protocol handshake requiring an upstream library rebuild. Since your Redis and PostgreSQL containers are running, I will trace whether the breakdown is inside the Go daemon socket or the Supabase Edge Function relay. Immediate execution plan: ✅ Snapshot and back up active PostgreSQL and Redis volumes prior to touching session state. ✅ Analyze Easypanel container and Traefik logs to capture the exact failure response on /instance/connect. ✅ Purge corrupted session keys in Redis and clear desynced instance rows in Postgres. ✅ Check Go WhatsApp library compatibility with current WhatsApp protocol revisions and rebuild/update the container image if required. ✅ Validate end-to-end flow: SaaS UI trigger, Supabase Edge Function call, QR payload delivery, and authenticated status update. Are existing connected WhatsApp numbers still communicating normally, or is the failure preventing both new pair attempts and active session reconnections?
$120 USD in 1 day
6.7
6.7

Your QR flow is breaking somewhere between the SaaS button, the Edge Function call, and EvolutionsGO’s instance connect route, so the real job is not just “making the QR appear” but finding where the payload stops being created and why the status never returns properly. I’d start by tracing that full path in logs and code, then check for stale Redis/Postgres session data and any library/version mismatch affecting the current EvolutionsGO install. I work a lot on debugging-based fixes where the issue sits across app logic, server config, and third-party/API behavior rather than in one obvious file. In a setup like yours on Easypanel + Supabase, the fastest route is usually to verify the request/response chain first, then clean broken instances and confirm whether the installed WhatsApp library layer is still compatible with the current build. - Which endpoint is currently being triggered from the SaaS screen when the user clicks connect? - Are you seeing any specific EvolutionsGO or Edge Function errors in logs right now? - Has anything changed recently such as an update, deploy, library version, or Cloudflare/Traefik rule before QR generation stopped?
$250 USD in 1 day
6.8
6.8

When EvolutionsGO stops emitting QR payloads while PostgreSQL and Redis look healthy, the usual cause is an outdated whatsmeow client that WhatsApp now rejects, or a stale session blocking /instance/connect. Every hour down means clients can't onboard. Quick questions - is the Supabase Edge Function getting an error from /instance/connect, or timing out behind Traefik? And are you pinned to a specific EvolutionsGO release, or building from source in Easypanel? Here is the architectural approach: - EVOLUTIONSGO LOGS: Trace /instance/connect in Easypanel to pinpoint where the QR payload fails, whether auth, protocol, or webhook. - REDIS/POSTGRESQL: Back up, then purge crashed or corrupted instance sessions so live customer connections stay intact. - SUPABASE EDGE FUNCTION: Update the
$130 USD in 3 days
7.1
7.1

Linux-based troubleshooting across your Easypanel/Ubuntu infrastructure is the strongest match I offer for restoring this EvolutionsGO QR connection flow. I can work with your server environment, inspect application logs, trace the connection route and Edge Function integration, and identify whether the failure is occurring in the API, Redis/PostgreSQL session state, or the SaaS callback. My Linux and JavaScript/Node.js background supports practical debugging of backend services and REST API workflows, while my experience building automation systems and integrations helps me follow the full path from the SaaS action through the API response and UI status update. I can also investigate crashed or stale instances in the local databases and verify whether the deployed EvolutionsGO/WhatsApp library combination is contributing to the issue, without making unsupported changes to the healthcare system. I am ready to apply this hands-on backend and infrastructure troubleshooting to restore QR generation and the connected status. Choose me to investigate the failure directly and work toward a reliable fix.
$110 USD in 4 days
5.9
5.9

Hey, the detail that stands out is that new connections stopped generating the QR code while the databases are fine. When it starts suddenly like that, the usual cause is WhatsApp rejecting an outdated client version during pairing, not a problem in your own code. Evolution GO is built on whatsmeow, not Baileys, so the first thing I'd check is which whatsmeow version your build uses and whether a newer Evolution GO release already fixes this. I'd start with the Evolution GO logs in Easypanel while triggering a new connection, to see whether the connect route returns an error, an empty payload, or just times out. Then I'd follow the call back through the Supabase Edge Function, because a timeout there can look like a missing QR code even when the API responds late. Next, I'd clean out any stuck or half-created instances in Redis and Postgres without touching the sessions that are working. Since this is a healthcare system, I'd back up both databases before deleting anything. Last, I'd test the full flow, from clicking the button in the SaaS, to the QR code showing, to the status changing to "connected." Are the customers who were already connected still working normally, or have existing sessions dropped too? Juan Pablo
$140 USD in 7 days
6.2
6.2

Hello, I have carefully read your project description and understand that you are looking for a specialist in Evolution API (Go) and Supabase to urgently debug and resolve a critical QR code generation failure in your healthcare SaaS system running on Easypanel with PostgreSQL, Redis, and Cloudflare. To approach your project I will inspect Evolution API container logs in Easypanel, diagnose the instance connection route payload failures, clean up corrupted sessions in Redis and PostgreSQL, and verify WhatsApp/Baileys compatibility to ensure that the final deliverable not only meets but exceeds your expectations. My focus will be on restoring the complete Edge Function-to-API connection flow and reestablishing seamless QR code generation while maintaining a seamless workflow. In terms of relevant experience, I have years of experience in Evolution API (Go) implementations, Supabase backend development, PostgreSQL and Redis session management, and Easypanel infrastructure troubleshooting. I have extensive expertise in relevant tools like Evolution API, Go, Supabase, PostgreSQL, Redis, Docker, and Easypanel. Could you share when this failure first started occurring and whether any recent updates were pushed to Evolution API or your Supabase Edge Functions? I’d love to discuss your project further and get started on resolving this immediately. Feel free to provide access credentials whenever you are ready. Best Regards, Rabia Shaikh.
$100 USD in 2 days
5.6
5.6

I will urgently resolve the QR Code generation failure in your healthcare SaaS system so new WhatsApp connections generate QR codes and update status to 'connected' smoothly. To address the issue where the system stopped generating the QR Code on the SaaS screen, I will: - Analyze EvolutionsGO logs in Easypanel to identify the exact cause of the failure in the connection route (/instance/connect or similar) that prevents generating the QR Code payload. - Clean up possible crashed/corrupted sessions or instances stuck in your local databases (Redis/Postgres) running on Easypanel. - Validate whether the current version of EvolutionsGO requires a compatibility update with the WhatsApp library (Baileys/Go) to handle WhatsApp backend updates properly. - Reestablish the complete connection flow, ensuring that clicking your SaaS button triggers the Edge Function call, generates the QR Code payload, and updates the session status to 'connected'. Do you currently see any HTTP status errors in your Edge Function logs or Traefik proxy logs when triggering the connect route? On Freelancer.com I hold 4.9 stars from 153 reviews. Price: USD 150 in 2 days. - Adnan
$132.18 USD in 2 days
5.8
5.8

I can investigate the WhatsApp QR generation failure across EvolutionsGO, Easypanel, Redis/PostgreSQL, and Supabase Edge Functions. I’ll trace the connection flow from the SaaS button to the API endpoint, inspect logs and session state, identify version or configuration issues, and restore QR generation and connection status updates. I’ll also verify the fix with a fresh WhatsApp connection and avoid deleting existing sessions or data without a backup. I’m experienced with PHP, APIs, databases, and server-side debugging, but I won’t claim prior EvolutionsGO-specific experience without evidence. Can you share the current EvolutionsGO version and the relevant connection logs or error response?
$90 USD in 2 days
5.7
5.7

Hello, I took a look at your EvolutionsGO QR issue on the healthcare SaaS. Sounds like the WhatsApp side and the local DBs are fine, but the connect route is not handing the QR payload back to the screen. That usualy means a stuck session, a messy instance record, or the API version not lining up with Baileys no more. My plan is pretty straight forward. First I dig into the Easypanel logs around /instance/connect and see where the chain snaps. Then I clean up crashed or half dead sessions in Redis and Postgres so old junk is not blocking new QR. After that I check if your EvolutionsGO build needs a small bump for WhatsApp compatibility. Last step is a full walk through: SaaS button, Edge Function call, QR shows up, status flips to connected. I done similar Evolution API plus Supabase setups before, so I know where these things tend to hide. You open GitHub, Easypanel and Supabase access and I can get moving same day. Happy to wrap this up in a few days so your new connections work again.
$160 USD in 3 days
5.5
5.5

Hi, I am Nitish from Webcast Technology. A QR step that silently stops working usually leaves its answer in the server logs and in stale session state, not in the front-end button — so I would start there, tracing the /instance/connect call through Easypanel to find exactly where the payload drops. My approach would be to read the EvolutionsGO logs for the connect route first, then clear any crashed or corrupted sessions in Redis and Postgres, check whether the installed build needs a compatibility update with the Baileys/Go library, and finally retest the full flow from the SaaS button through the Edge Function until the QR renders and the status flips to connected. I have restored broken connection flows like this before — most recently a WordPress login and booking flow that had stopped authenticating users, where I traced the failure through the server logs, cleared the stale session data, and brought the login back end to end. Quick question — would you like me to begin with the Easypanel logs for the connect route, or with the Redis/Postgres session cleanup first? If that log-first order works for you, I can start the moment access is shared and have the failing step identified before any change is made to the live service. Nitish
$50 USD in 2 days
5.1
5.1

**Free right now and can start tracing your broken WhatsApp QR flow today** I am Anand. I can check your EvolutionsGO logs in Easypanel to find why /instance/connect is not returning the QR payload, clear crashed or corrupted sessions in Redis and PostgreSQL, check your EvolutionsGO version against the WhatsApp library for a compatibility break, and retest the full flow from the SaaS button through the Supabase Edge Function to QR generation and connected status. Recent work: Cleaned a compromised server in under a day and migrated 40+ sites to a hardened VPS with zero downtime. Can you share Easypanel and GitHub access so I start on the logs now?
$120 USD in 7 days
4.9
4.9

Hi there, I can help troubleshoot and fix the WhatsApp QR generation issue in EvolutionsGO, focusing on the integration between Evolution API, Supabase, and your application. I’ll trace the QR generation flow, inspect API requests and responses, verify session initialization and connection status, and identify why the QR code is failing to generate or display. I’ll then implement and test the fix while preserving the existing functionality. I’ll also check error handling and session refresh behavior to help prevent the issue from recurring. Let's connect through chat so I can understand the current failure and get the QR generation working reliably. Portfolio: https://www.freelancer.com/u/sf264 Ready to get your WhatsApp connection flow working correctly. Fahad
$100 USD in 1 day
5.3
5.3

Hi there, I can start on this right away. One thing I'd check first: Evolution GO runs on whatsmeow, not Baileys. When QR codes stop generating for new connections while existing ones keep working, the usual cause is an outdated whatsmeow version. WhatsApp raises its minimum client version from time to time and then rejects the pairing request. The logs should show that within a few minutes, and the fix is updating to the latest Evolution GO release and rebuilding the image in Easypanel. If it isn't that, I'll go through the whole chain step by step: SaaS button → Edge Function → /instance/connect → QR payload → webhook back to Supabase. I'll also clear out any stuck instances or sessions in Postgres and Redis, and check that Traefik isn't timing out or blocking the websocket. I'll take a backup before I delete anything, and since this is a healthcare system, I won't touch any patient data. Can you send me the error from the Evolution GO logs, and the date the QR codes stopped working? That might be enough to confirm the cause before I even log in. Thanks
$240 USD in 2 days
5.0
5.0

Hi, I’d trace the QR connection flow end to end before changing session data or upgrading dependencies. The key is to identify whether the failure originates in the EvolutionsGO connect endpoint, WhatsApp session initialization, the Supabase Edge Function, or delivery of the QR payload to the SaaS frontend. I’d start by checking Easypanel container logs, the deployed EvolutionsGO version, connect-request responses, and Redis/PostgreSQL session state. I’d then reproduce the failure with a test instance, verify the expected QR/event response, and check whether the frontend receives and renders it correctly. If corrupted sessions or a compatibility issue are responsible, I’d apply a targeted fix with backups in place rather than risk disrupting existing customer connections. Final validation would cover new QR generation, successful pairing, status updates, and regression checks on existing instances. One important detail: which exact EvolutionsGO repository or fork and version are you running, and what response or error appears when /instance/connect is called? Lets discuss on chat.
$140 USD in 7 days
5.6
5.6

My 14+ years of full-stack development experience, including Node.js, PostgreSQL, Linux, API integrations, Docker and cloud/DevOps work, directly match the infrastructure behind your EvolutionsGO QR connection issue. I can work across the SaaS flow, backend API, Edge Function integration and Easypanel server rather than treating the missing QR as only a frontend problem. My experience with PostgreSQL and Linux is relevant to inspecting the API environment, logs and persisted connection data, while my Node.js and REST API background supports tracing the request from the SaaS button through `/instance/connect` and the QR payload response. I can also review Redis/Postgres session state, identify failed or stale instances, and verify whether the installed WhatsApp API version or integration is causing the break. I am ready to investigate this urgently and restore the connection flow through to the `connected` status. Choose me to troubleshoot the issue across the application, server and database layers.
$140 USD in 7 days
5.0
5.0

My PostgreSQL and Node.js experience is directly relevant to tracing the failed QR-generation flow across your SaaS and EvolutionsGO integration. I can investigate the connection request, inspect the API response and logs, and identify whether the failure is occurring in the Edge Function, instance route, or database state. I also work with PostgreSQL and MySQL, which supports reviewing and safely cleaning corrupted or stalled session records while preserving the healthcare SaaS data. My Node.js background is valuable for following the application logic between the button click, API call, QR payload, and connection-status update. Although my profile focuses on web and e-commerce development, these backend skills align with debugging the integration layer and restoring the user flow. I’m ready to apply my PostgreSQL and Node.js skills to this urgent EvolutionsGO issue and help restore reliable QR generation and connection handling.
$69 USD in 4 days
4.7
4.7

Hi, A QR code that never shows up usually means an old instance session is still stored in Redis or Postgres and blocking new connections. Clearing those stale sessions is often the quickest way back to connected status. We'd start there, then follow one connect request from the SaaS button through the Edge Function to find the step where it stalls, and fix that so QR generation works again. Could you share the EvolutionsGO logs from a failed connect request? WhmDesign LLC
$250 USD in 7 days
4.7
4.7

United States
Payment method verified
Member since Oct 6, 2026
$30-250 USD
$30-250 USD
$250-750 USD
₹12500-37500 INR
₹600-1500 INR
₹1250-2500 INR / hour
$15-25 USD / hour
$10-30 USD
$15-25 CAD / hour
₹1500-12500 INR
$250-750 USD
$10-30 USD
$250-750 USD
₹12500-37500 INR
$80-85 USD / hour
$250-750 USD
$30-250 USD
$750-1500 USD
$8-15 USD / hour
₹12500-37500 INR
₹1500-12500 INR
₹1500-12500 INR