panic: pq: SSL is not enabled

[doronbehar]

I get an error when running the server with the following configuration:

server:
  port: 8001 # the port for the http server
  ssl:
    enabled: false # if https should be enabled
    redirecttohttps: true # redirect to https if site is accessed by http
    port: 8002 # the https port
    certfile: /etc/letsencrypt/live/doronbehar.com/fullchain.pem # the cert file (leave empty when using letsencrypt)
    certkey: /etc/letsencrypt/live/doronbehar.com/privkey.pem # the cert key (leave empty when using letsencrypt)
    letsencrypt:
      enabled: false # if the certificate should be requested from letsencrypt
      accepttos: false # if you accept the tos from letsencrypt
      cache: data/certs # the directory of the cache from letsencrypt
      hosts: # the hosts for which letsencrypt should request certificates
      - doronbehar.com
database: # for database see (configure database section)
  dialect: postgres
  connection: host=localhost port=5432 user=gotify dbname=gotify password=xxx

defaultuser: # on database creation, gotify creates an admin user
  name: admin # the username of the default user
  pass: admin # the password of the default user
passstrength: 10 # the bcrypt password strength (higher = better but also slower)
uploadedimagesdir: data/images # the directory for storing uploaded images

Error message:

Starting Gotify version 1.2.0@2018-11-24-11:06:13
Failed to find configuration config.yml
panic: pq: SSL is not enabled on the server

goroutine 1 [running]:
main.main()
        /home/travis/gopath/src/github.com/gotify/server/app.go:44 +0x425

The same error appears when enabling and disabling ssl.

[jmattheis]

It's probably not a problem with the server ssl. It's a problem with the database connection.

Could you try to add sslmode=disable to your connection string

connection: host=localhost port=5432 user=gotify dbname=gotify password=xxx sslmode=disable

See https://stackoverflow.com/questions/21959148/ssl-is-not-enabled-on-the-server

[doronbehar]

That worked, my server is up and running, thanks. This flag is not documented right?

Additionally, Why is there the Failed to find configuration config.yml message when it does exist in it's default location /etc/gotify?

[jmattheis]

Yeah, I'll add this flag to the readme. The config library Gotify uses, outputs this message for every location where it couldn't find a config file, but yeah it is a little missleading and should be fixed.

[doronbehar]

Thanks for your help, I've one more question please: I'm having trouble making use of my server because from some reason I can't log in with the default username and password.

I've tried using both the PostgreSQL server and both the SQLite file and I can see a user is created with a hashed password but the login just fails. I've tried to delete the SQLite file and rerun the server and I've tried to drop the gotify table in PostgreSQL's shell and recreate it and rerun gotify afterwards but still the default username and password don't work.

Perhaps it could be because I run it behind a reversed proxy connection Apache server?

[jmattheis]

@doronbehar could you try connecting to Gotify without the reverse proxy? Is your proxy pointing to a subdomain?

[doronbehar]

Weirdly, the authentication works fine when I use the same credentials without the proxy and directly to port 8001.

My setup is as follows:

I run gotify without it's builtin SSL support on port 8001 - as seen in my config.yml. I have a <VirtualHost> section in my httpd.conf:

<VirtualHost _default_:80>
    ServerName gotify.doronbehar.com
    Redirect permanent / https://gotify.doronbehar.com/
</VirtualHost>

<VirtualHost _default_:443>
    ServerName gotify.doronbehar.com
    <Proxy *>
        AuthType Basic
        AuthName "Protected site"
        # Just for extra protection
        AuthUserFile /etc/gotify/.htpasswd
        Require valid-user
        Order deny,allow
        Allow from all
    </Proxy>
    ProxyPassMatch ^/.well-known/acme-challenge/ !
    ProxyPass "/" "http://localhost:8001/" connectiontimeout=5 timeout=30 keepalive=on
    ProxyPassReverse "/" "http://localhost:8001/"
    ErrorLog /var/log/httpd/gotify.info-error_log
    CustomLog /var/log/httpd/gotify.info-access_log common
    SSLEngine on
    BrowserMatch "MSIE [2-5]" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
        SSLOptions +StdEnvVars
    </FilesMatch>
    SSLCertificateFile /etc/letsencrypt/live/doronbehar.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/doronbehar.com/privkey.pem
    Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>

EDIT

BTW I've just checked on the login with the app and that works just fine. I think my problem was that basic authentication for the server. So problem solved.

Thanks anyway.

[jmattheis]

@doronbehar Yeah, it's probably the fault of the added basic auth for the proxy, Gotify also uses basic auth for authentication, so maybe it's not that easy to have both.

[doronbehar]

Then besides the config.yml message I see this issue as closed, thanks again for your help I hope I'll find Gotify useful for me.

[jmattheis]

I created #93 for missleading error message. Also I'll document the sslmode flag. Thanks for trying out Gotify (:.

[nishanth1301]

Started Listening for plain HTTP connection on :80
2023/04/25 08:59:10 Could not listen on :80 listen tcp :80: bind: address already in use
got error while running in niginx

[jmattheis]

@nishanth1301 it's unrelated to this ticket, please create a new ticket. Gotify tries to start a http server on port 80, but there is already something running on that port.