Skip to content

Server no longer working after restart #418

Open
@mikebel3

Description

@mikebel3

My instance is running in docker on a synology created using a portainer stack. This is the error message from the Docuseal container. All the containers (DocuSeal, DocuSeal-DB, and Docuseal-REDIS) show as healthy.

Puma starting in single mode...

  • Puma version: 6.5.0 ("Sky's Version")

  • Ruby version: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux-musl]

  • Min threads: 15

  • Max threads: 15

  • Environment: production

  •      PID: 1
    

WARNING: Nokogiri was built against libxml version 2.13.5, but has dynamically loaded 2.13.4

I, [2025-01-09T17:22:38.001914 #1] INFO -- : Migrating to CreateTemplateAccesses (20241207172237)

== 20241207172237 CreateTemplateAccesses: migrating ===========================

-- create_table(:template_accesses)

-> 0.0878s

== 20241207172237 CreateTemplateAccesses: migrated (0.0880s) ==================

Use Ctrl-C to stop

2025-01-09T17:22:39.994Z pid=1 tid=ch5 INFO: Sidekiq 7.3.7 connecting to Redis with options {size: 10, pool_name: "internal", url: "redis://:REDACTED@docuseal-redis:6379/0"}

2025-01-09T17:22:40.046Z pid=1 tid=chl INFO: Sidekiq 7.3.7 connecting to Redis with options {size: 5, pool_name: "default", url: "redis://:REDACTED@docuseal-redis:6379/0"}

2025-01-09T17:22:40.046Z pid=1 tid=cht INFO: Sidekiq 7.3.7 connecting to Redis with options {size: 5, pool_name: "default", url: "redis://:REDACTED@docuseal-redis:6379/0"}

2025-01-09T17:22:40.046Z pid=1 tid=ci1 INFO: Sidekiq 7.3.7 connecting to Redis with options {size: 5, pool_name: "default", url: "redis://:REDACTED@docuseal-redis:6379/0"}

2025-01-09T17:22:40.046Z pid=1 tid=ci9 INFO: Sidekiq 7.3.7 connecting to Redis with options {size: 5, pool_name: "default", url: "redis://:REDACTED@docuseal-redis:6379/0"}

2025-01-09T17:22:40.047Z pid=1 tid=cih INFO: Sidekiq 7.3.7 connecting to Redis with options {size: 5, pool_name: "default", url: "redis://:REDACTED@docuseal-redis:6379/0"}

2025-01-09 17:23:49 +0000 HTTP parse error, malformed request: #<Puma::HttpParserError: Invalid HTTP format, parsing fails. Are you trying to open an SSL connection to a non-SSL Puma?>

2025-01-09 17:23:49 +0000 HTTP parse error, malformed request: #<Puma::HttpParserError: Invalid HTTP format, parsing fails. Are you trying to open an SSL connection to a non-SSL Puma?>

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