Troubleshooting
Troubleshooting
Find the message you see, then read the cause and the fix. Messages are quoted
from the source; ... marks a part that varies.
The server will not start
| Message | Cause | Fix |
|---|---|---|
refusing to start: no session signing key configured (PULSE_JWT_SECRET unset) | PULSE_JWT_SECRET is unset | Set it to a new random value. There is no default and none is generated. |
refusing to start: the pulse appfs root cannot be mounted: ... | The sealed app root has no usable backend | Check the object store settings, or PULSE_APPFS_DIR for a local root. |
Failed to initialize database: ... | Usually TIDE_ENVELOPE_KEK is missing; the database refuses to open without it | Project the key. |
refusing to start in production: insecure configuration: ... | PULSE_ENV=production and a check failed | Fix each listed problem. For the CORS problem, set CORS_ALLOWED_ORIGINS to pinned origins (no wildcard); the backend serves no web bundle, so there is no same-origin exemption. |
TLS misconfigured: set BOTH PULSE_TLS_CERT and PULSE_TLS_KEY (or neither) | Only one of the two is set | Set both, or neither. |
MESH_MTLS=true but mesh identity unavailable: ... | No mesh identity could be set up | Provide MESH_ISSUER_URL and MESH_CA_CERT (preferred), or the older MESH_CA_CERT and MESH_CA_KEY; or turn off MESH_MTLS. |
| Server exits with no output, no log file | Locally: pkill -f 'pulse-server serve' matches the shell running that command, so it kills your own session | Stop the server by its PID instead. |
address already in use | A previous server holds the port | Stop it by PID, then restart. |
Signing in
| Message | Cause | Fix |
|---|---|---|
invalid credentials | Wrong username or password; you used your email instead of your username; or no break-glass admin was seeded | Sign in with the username. On a local server, start it with PULSE_ADMIN_PASSWORD. |
authorization token is not provided | The call had no bearer token | Send authorization: Bearer <accessToken>. |
invalid token: ... | The token expired, or its session was signed out | Sign in again. |
a cookie session requires the x-pulse-csrf header and a trusted Origin | A browser call authenticated by the session cookie arrived without the x-pulse-csrf: 1 header, or from an origin this deployment does not trust | Use the app served by this deployment. For a separate front-end origin, add it to CORS_ALLOWED_ORIGINS exactly; a wildcard is never accepted. |
token contains an invalid number of segments | A script read .token; the field is accessToken | Read accessToken. |
Google sign-in: “not set up on this PULSE” (/auth/google answers not_configured) | Google sign-in is off | Set GOOGLE_CLIENT_ID. |
Google sign-in: “Nobody can sign in with Google on this PULSE yet” (sso_closed) | AUTH_ALLOWED_EMAILS is empty | Add the allowed addresses. |
Google sign-in: “… is not on this PULSE’s list of people allowed to sign in” (not_allowed) | The email is not on the allowlist | Add it to AUTH_ALLOWED_EMAILS. |
Google sign-in: “Google signed you in for a different app” (wrong_client) | The ID token was issued to another OAuth client than GOOGLE_CLIENT_ID | Use the web client’s ID in GOOGLE_CLIENT_ID; the Android app asks Google for a token for that same client. |
| Android: “This copy of the app is not registered with Google yet” | The Google project of GOOGLE_CLIENT_ID has no Android OAuth client for org.runink.pulse with the SHA-1 of the key the installed app is signed with | Add one for each signing key in use: the Play App Signing key (Play Console → App integrity) and the upload or debug key for builds installed outside Play. |
| Linux app: “Google sign-in is not available in this app on this device” | The Google sign-in library has no Linux desktop support | Sign in with a username and password, or use PULSE in the browser. |
license expired or invalid | A configured licence failed verification | Install a valid licence. |
Log: AUTHENTICATION DISABLED — every request will be rejected as Unauthenticated | This deployment’s session key is one PULSE refuses to sign or verify with, so no token can be accepted | Replace PULSE_JWT_SECRET with a fresh value that has never been committed to a repository, and restart. |
AI features
| Message | Cause | Fix |
|---|---|---|
inference server is not running / model service is not ready — the inference server is not running | No inference server, or it is still loading | Check INFERENCE_REMOTE_URL or the local model files. Watch model_ready on /health. |
the inference plane is at capacity and declined this request; nothing was generated — retry in a few minutes | Admission control refused the call | Retry later, or raise PULSE_ADMIT_MAX. |
... Nothing was dispatched. Raise PULSE_GENERATION_TIMEOUT_SECONDS, serve a faster tier, or ask for less | The time budget is too short for the decode rate | Raise PULSE_GENERATION_TIMEOUT_SECONDS, serve a faster model, or ask for less. |
the model returned no content for ... | The model produced an empty response | Retry. Check the inference server’s log. |
still-image generation is not available: the image-generation tier was retired ... | Still images are not supported | Request a video format instead. |
grounding: no data/corpus directory in the log | The image was built without grpc/data/corpus | Rebuild the image from the repo. Whitepapers still generate, but say they are ungrounded. |
Site score and audit fixes
| Message | Cause | Fix |
|---|---|---|
could not read ... — a reachable website with readable content is required to run the diagnostic | PULSE could not load the site | Check the URL is public and returns readable HTML. |
url is required / repo_path is required | A field is missing in ApplyAuditActions | Fill it in. |
apply modes are disabled on this server; set PULSE_APPLY_ENABLED=true (exactly, lowercase) and PULSE_AUDIT_APPLY=true to allow write/commit/pr | The kill switch or PULSE_AUDIT_APPLY is off | Use plan, or have an admin arm both. |
apply modes require an administrator | Your role is not admin | Ask an admin to apply the fixes. |
repo_path is not an allowed repository on this server | The path is outside PULSE_APPLY_ROOT, missing, or escapes it | Use a checkout inside the root. |
audit apply has no repository root on this server; an administrator must set PULSE_APPLY_ROOT | PULSE_APPLY_ROOT is unset | Set it to the directory holding site checkouts. |
github integration is missing a target owner/repo — ... | pr mode without a target | Set owner and repo on the GitHub connection. |
scoring config: ... | PULSE_SCORING_CONFIG is unreadable or invalid, or the profile is unknown | Fix the file or the profile name. |
The one-line audit
| On the audit card | Cause | Fix |
|---|---|---|
"…" is not a domain (expected something like example.com) | You gave an IP address, localhost, or something that is not a host name | Type a public domain, for example Audit example.com. |
| Nothing happens; the assistant answers in chat instead | The line has a question mark, or no verb it recognizes | Write Audit example.com, with no ?. See Audit a domain. |
| Waiting for the model (position N in the queue) | Another audit’s model calls are ahead of yours | Nothing. Your steps run in turn. |
Publishing schedule is skipped: no draft to put the plan's times on | The plan had no draft to carry its dates | Expected. The tasks are on the 90-day plan; the audit is not partial because of it. |
| A post in the Scheduled column of Campaigns says missed | Its time passed while the piece was waiting for approval | Reschedule it, or remove it. A missed post is never sent late. |
A step is skipped with blocked: … | A step it needs did not finish, for example blocked: the site could not be read (…) | Fix the first failed step, then Resume the audit. |
A phase reads … — not completed within the 3-minute budget | The diagnosis runs to one end-to-end deadline of about three minutes. A phase that did not finish inside it is reported as not done rather than left to look finished | Expected under load. Run it again when the inference server is quieter, or an administrator can raise PULSE_AUDIT_DEADLINE_SECONDS. |
diagnosis: … or the analysis was written but no plan was produced | The model returned nothing usable, or the plan step failed | Resume the audit. Steps already done are not repeated. |
every lead discovery search failed (…) — the web was not reached | No lead search answered | Check the server’s web access, then resume. |
this domain was audited at … UTC (less than 24h ago) — returning that run | A finished audit of the domain is less than a day old | Use Run it again to force a fresh one. |
PermissionDenied when you start an audit | Your role is viewer | Ask an admin to make you an editor. |
Leads and connections
| Message | Cause | Fix |
|---|---|---|
HubSpot isn't connected yet — configure it on the Integrations page first | No HubSpot connection | Connect it on the HubSpot card in Settings → Integrations. |
HubSpot integration has no access token configured | The connection has no token | Rotate the credential. |
HubSpot sync failed: ... | HubSpot rejected the call | Check the token’s scopes. |
unsupported lead platform: ... (only hubspot is supported today) | SyncLeads with another platform | Use hubspot. |
a niche is required to prospect for leads | ScrapeLeads without a niche | Provide one. |
a lead needs at least a name, email, or company | Empty CreateLead | Fill one in. |
invalid pipeline stage "..." (want new|contacted|qualified|won|lost) | Unknown stage | Use one of the five. |
outbound calling is disabled on this server; an administrator must set PULSE_OUTBOUND_CALLS=true | Calls are not armed | Have an admin set it. |
outbound calls require an editor or administrator | Your role is viewer | Ask an admin to change your role. |
Scheduled post withheld: ... is owner-gated: user "<user-id>" is not in PULSE_PUBLISHER_USER_IDS | The channel publishes as the deployment and the content’s owner is not allowlisted | Add the owner’s user id, or leave it withheld. |
/podcast/feed.xml returns 404 | Both podcast and audiobook are disarmed | Arm one, if the feed should exist. |
lead has no phone number | Nothing to dial | Add a phone number. |
Google Analytics isn't connected yet — configure it on the Integrations page first | No GA4 connection | Connect it on the Google Analytics card in Settings → Integrations. |
no GA4 property ID configured — set it when connecting Google Analytics | The connection lacks a property ID | Reconnect with the property ID. |
A forecast shows history only (too_few_days) | Fewer than four days of Google Analytics data are synced | Run SyncGaData with a longer lookback. |
Sign-in connections and the website repository (administrators)
| Message | Cause | Fix |
|---|---|---|
Instagram sign-in isn't set up on this server yet: an administrator must set META_APP_ID and META_APP_SECRET (also YouTube … GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, LinkedIn … LINKEDIN_CLIENT_ID and LINKEDIN_CLIENT_SECRET) | The platform’s app client is not configured | Set both keys; see Meta, Google, LinkedIn. Until then the card accepts a pasted token. |
… sign-in isn't set up on this server yet: an administrator must set PULSE_PUBLIC_BASE_URL to the https address the sign-in returns to | PULSE_PUBLIC_BASE_URL is unset or not https | Set the https address; see Public address and redirects. |
Company pages aren't set up on this server yet: … | LINKEDIN_COMPANY_PAGES is off | Turn it on only after LinkedIn approved the Community Management API. |
| The platform says the redirect URI does not match | The callback is not registered exactly in the developer console | Register <PULSE_PUBLIC_BASE_URL>/oauth/social/callback (or /oauth/search-console/callback, /oauth/mail/callback), https, no trailing slash. |
| Sign-in completes at the platform but the card stays not connected | The TIDE edge sent the callback to the web app, or the connect link was older than ten minutes | Route the /oauth/…/callback paths to the backend; start the connection again. |
your Search Console properties could not be read: … | The Google Search Console API is not enabled in the client’s project, or the account has no property | Enable the API; add the site to Search Console. |
GitHub rejected the website repository token; reconnect it in Settings → Integrations | The token expired or was revoked | Create a new fine-grained token and reconnect. |
GitHub refused to …: the token is missing a permission (…) | The token lacks Contents or Pull requests (read and write), or does not cover the repository | Regenerate it with both permissions on that repository. |
apply modes are disabled on this server; … on Propose as pull request | PULSE_APPLY_ENABLED or PULSE_AUDIT_APPLY is off | Arm both, if proposals are wanted. |
No video was made: video is not available on this server. | ffmpeg is missing from the server | Use the backend image (it ships ffmpeg) or set FFMPEG_PATH. |
Publishing
| Message | Cause | Fix |
|---|---|---|
website publishing is disabled: ... | The blog channel is not armed | See Publishing controls. The message names the layer. |
PULSE_SITE_REPO is not set — refusing to publish; set it to YOUR site repo as owner/repo | No target repository | Set PULSE_SITE_REPO. |
no github integration/token configured for user ... | The content owner has no GitHub token | Paste one on the Website card in Settings → Integrations. |
no publishing integration for channel ... yet | The post was scheduled to a channel PULSE drafts for but does not post to, for example Facebook or X | Download it and post it yourself. See Publishing. |
A scheduled post shows withheld | Its channel was disarmed when it came due | Arm the channel, then schedule the content again. |
LinkedIn post withheld: LinkedIn publishing is not configured: … (drafts-only: the content stays approved for manual posting) | No LinkedIn token or author is configured | Expected on a drafts-only deployment. Download it from its card and post it by hand. |
Log: PUBLISHCFG-AMBIGUOUS PULSE_APPLY_ENABLED=... | The value is not exactly true | Write true, lowercase. |
Voice, billing, media
| Message | Cause | Fix |
|---|---|---|
voice calling is not configured: CALLING_AGENT_URL is unset (HTTP 503) | No calling agent | Set CALLING_AGENT_URL. |
speech synthesis is not configured | TTSD_URL is set to empty, or TIDE’s ttsd is not available | Unset TTSD_URL to use the in-cluster service, or point it at ttsd. See Voice. |
media storage is not available: ... / media unavailable | The sealed media store is not mounted | Check the app root’s backend. |
Strip: Daily limit reached: tasks keep running on reduced compute until … | A trial seat has used its full-speed tasks for the day | Expected. Tasks keep running at a slower pace and the count resets at midnight on the seat’s clock. See Plans. |
Strip: We can't check your daily limit right now, so tasks run on reduced compute. | The billing service could not be reached, so PULSE assumes the slower pace rather than guessing | Retry later. Work still runs. |
Log: Site Audit Engine: NOT started — no target site; ... | No daily audit target | Set PULSE_SITE_AUDIT_URL. |
The app looks empty
PULSE never fills a gap with an estimate. A figure it could not read is drawn
as —, and a page with nothing behind it reads as empty rather than as a row
of zeros. An empty page is usually a missing input, not a fault.
- Brand Analysis says “No check-up yet”, and its cards say “Not checked yet”. Choose New site audit. See Getting started.
- Results read “Not measured”. Nothing measured the period yet. Connect Google Analytics, Google Ads or Search Console in Settings → Integrations. The work PULSE did is still counted, under What PULSE did. See Results and reports.
- “Results of your posts: not measured yet”. No platform reported results for your posts this week: connect Instagram, LinkedIn or YouTube, or wait for the first results after a post goes out.
- Campaigns has no drafts, and Leads has no tasks. Run a check-up. A finished check-up fills them.
- A card shows
—where you expected a number. PULSE could not read that figure — usually a connection that is not set up, or a run that has not happened yet. Nothing is wrong with the card. See Measured and not measured.
Connecting accounts and planning
| What you see | Cause | Fix |
|---|---|---|
| … sign-in isn’t set up on this server, with a list of settings | Your administrator has not registered PULSE with that platform | Paste a token instead, or ask your administrator to set what the card lists. See Connections. |
| The sign-in has ended. Reconnect … to keep publishing. | The platform ended the sign-in, or renewing it failed | Reconnect on the card. |
| Missing permission: …. Reconnect and allow it. | You declined a permission when signing in | Reconnect and allow it. |
| The sign-in page could not be opened | The browser blocked the pop-up | Allow pop-ups for PULSE and try again. |
| This Google account has no verified site in Search Console | The Google account you signed in with owns no Search Console property | Add your site at search.google.com/search-console, then reconnect. |
| Website repository: Missing permission, Token rejected or Base branch not found | The fine-grained token lacks Contents or Pull requests (Read and write), has expired, or the branch name is wrong | Fix the token or the branch, then Check again. See Website repository. |
connect your website repository in Settings → Integrations first | Propose as pull request with no repository connected | Connect it. |
PULSE does not know who you talk to yet: run a site audit (it asks who buys from you) or add leads, then plan again | A campaign plan needs at least one persona | Run a check-up, or add leads, then plan again. |
| This can’t move from … to … / A post moves to Sent only when it goes out. | A move the board does not allow | See Approve and schedule. |
| Not connected, so PULSE will not post it | The piece’s channel has no connected account | Download it and post it yourself, or connect the channel. |