Skip to content

heartbeat check fails for tutamail #816

@kibibytium

Description

@kibibytium

We want to release our new tutamail app but we fail to enable it currently.

The heartbeat check fails as follows:

Failed heartbeat on http://nextcloud.tuta/exapps/tutamail for 30 times. Most recent status=0, error: Server error:
`GET http://nextcloud.tuta/exapps/tutamail/heartbeat` resulted in a `503 Service Unavailable` 
response: <html><body><h1>503 Service Unavailable</h1> No server is available to handle this request. </body></html>

Some notes:

  • The endpoint /heartbeat is reachable using the docker container's IP directly.
  • The reverse proxy in front of the Nextcloud server proxies http://nextcloud.tuta/exapps to the HaRP proxy on port 8780.
  • Test deploy works
  • Other ExApps work.

Should the ExApp expose the ports it runs on or define them somehow? If so, how?

Here is the app on the app store:
https://apps.nextcloud.com/apps/tutamail

The code is on a branch here:

https://github.com/tutao/tutanota/tree/nextcloud/integrations/nextcloud/tutamail

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions