gitroomhq/postiz-app · error · Error

Failed to create MeWe post

Error message

Failed to create MeWe post

What it means

MeWe post creation returned a non-ok response whose body did not match any known error pattern in handleErrors, so a generic 'Failed to create MeWe post' is thrown. The raw response is in errorText but not surfaced.

Source

Thrown at libraries/nestjs-libraries/src/integrations/social/mewe.provider.ts:280

    const postUrl =
      postType === 'timeline'
        ? `${this.meweHost}/api/dev/me/post`
        : `${this.meweHost}/api/dev/group/${groupId}/post`;

    // MeWe post endpoint may return 204 (no content), so use raw fetch
    const postResponse = await fetch(postUrl, {
      method: 'POST',
      headers: this.authHeaders(accessToken),
      body: JSON.stringify(postBody),
    });

    if (!postResponse.ok) {
      const errorText = await postResponse.text();
      const handleError = this.handleErrors(errorText);
      if (handleError) {
        throw new Error(handleError.value);
      }
      throw new Error('Failed to create MeWe post');
    }

    const postId = makeId(12);

    const releaseURL = postType === 'timeline' ? `https://mewe.com/${integration.profile}/posts` : `https://mewe.com/group/${firstPost.settings.group}`;

    return [
      {
        id: firstPost.id,
        postId,
        releaseURL,
        status: 'success',
      },
    ];
  }
}

View on GitHub (pinned to 0f1647f749)

Solutions

  1. Log/reproduce the request and inspect the raw response body (errorText) to identify the cause
  2. Re-authenticate the MeWe integration (CSRF/session cookies)
  3. Check whether MeWe changed its private API — update headers/payload accordingly
  4. Retry once for transient 5xx responses
Defensive patterns

Strategy: fallback

Try / catch

catch (e) { if ((e as Error).message === 'Failed to create MeWe post') { logRawResponseForDiagnosis(); await reconnectMewe(); } }

Prevention

When it happens

Trigger: POST to MeWe's post endpoint returns non-2xx with an unrecognized body (HTML error page, changed API contract, unexpected status code).

Common situations: MeWe private API changed shape, server-side 5xx, CSRF token missing/expired, or payload MeWe rejects silently.

Related errors


AI-assisted analysis of gitroomhq/postiz-app@0f1647f749 (2026-08-27). Data as JSON: /api/errors/9eed1b5a30a9ff31. Report an issue: GitHub.