Project

General

Profile

Actions

Bug #14694

closed

HAProcy

Added by Rick Strangman over 1 year ago. Updated over 1 year ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
haproxy
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
21.05.1
Affected Architecture:
i386

Description

After the latest update I can no longer assign an ACME certificate to a HAProxy Frontend, not matter which certificate it is. Error generated is:
Errors found while starting haproxy
[NOTICE] (86157) : haproxy version is 2.7.6-4dadaaa
[NOTICE] (86157) : path to executable is /usr/local/sbin/haproxy
[ALERT] (86157) : config : parsing [/var/etc/haproxy_test/haproxy.cfg:43] : 'bind 172.21.22.23:443' in section 'frontend' : 'crt-list' : unable to load certificate from file '/var/etc/haproxy_test/HTTPS_Frontend/HTTPS_netch.au_633b5acc820cd.pem': no start line.
[ALERT] (86157) : config : Error(s) found in configuration file : /var/etc/haproxy_test/haproxy.cfg
[ALERT] (86157) : config : Fatal errors found in configuration.

The certificate is indeed in the folder /var/etc/haproxy_test/HTTPS_Frontend/HTTPS_netch.au_633b5acc820cd.pem and the certificate looks valid

Actions #1

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Not a Bug

I'm using ACME certs with HAProxy and it works fine here, so it's not clear why yours might be failing.

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum .

See Reporting Issues with pfSense Software for more information.

Actions

Also available in: Atom PDF