Skip to content

HTTPS only mode (disable HTTP Permanently) #910

Open

Description

@IzumiSenaSora

Have you read the documentation?

  • Yes, but it does not include related information regarding my question.
  • Yes, but the steps described in the documentation do not work on my machine.
  • Yes, but I am having difficulty understanding it and want clarification.

You are setting up gotify in

  • Docker
  • Linux native platform
  • Windows native platform

Describe your problem

I want to disable plain HTTP completely and only use HTTPS only but don't know how i can disable it completely
Can someone help me a bit

Any errors, logs, or other information that might help us identify your problem

Ex: docker-compose.yml, nginx.conf, android logcat, browser requests, etc.

Name of the information here

contents here

Activity

  1. eternal-flame-AD commented on Feb 6, 2026

    @eternal-flame-AD
    Member

    I don't think this is possible for now, the built in TLS server is rather bare bones (no HTTP/3 and quic stuff), for now I recommend using a reverse proxy to do TLS termination which is a more robust architecture.

    We could make port number -1 as a magic number for disable though.

  2. IzumiSenaSora commented on Feb 6, 2026

    @IzumiSenaSora
    Author

    I don't think this is possible for now, the built in TLS server is rather bare bones (no HTTP/3 and quic stuff), for now I recommend using a reverse proxy to do TLS termination which is a more robust architecture.

    We could make port number -1 as a magic number for disable though.

    Sometimes even though it's bare bone!
    I need TLS mode cause nginx in other server so in between two server i want to gotify to be secure!
    So already enabled TLS and it's working flawlessly behind nginx!
    Just want to disable Plain HTTP

    If possible please add support for port "-1" to disable it
    Thanks in advance

  3. jmattheis commented on Feb 7, 2026

    @jmattheis
    Member

    @IzumiSenaSora You could set the listenaddr 127.0.0.1, then the http endpoint won't be exposed to the outside. Is this the problem you are trying to solve?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions