Project

General

Profile

Actions

Bug #9429

closed

When enabling https access to WebConfigurator

Added by P L over 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
-
Start date:
03/24/2019
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:

Description

Running pfSense dev 2.5.0.a.20190322.1846 release (though issue is not new).

When I enable https for "System -> Advanced -> Admin Access -> webConfigurator", I receive the following error messages in "Status -> System Logs -> System -> General" and I am unable to login.

Mar 24 15:17:24 php-fpm 73685 /rc.restart_webgui: The command '/usr/local/sbin/nginx -c /var/etc/nginx-webConfigurator.conf' returned exit code '1', the output was 'nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to [::]:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to [::]:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to [::]:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to [::]:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to [::]:443 failed (48: Address already in use) nginx: [emerg] still could not bind()'
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: still could not bind()
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to [::]:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to [::]:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to [::]:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to [::]:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to [::]:443 failed (48: Address already in use)
Mar 24 15:17:21 nginx 2019/03/24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use)
Mar 24 15:17:19 check_reload_status 340 webConfigurator restart in progress
Mar 24 15:17:19 php-fpm 327 /system_advanced_admin.php: webConfigurator configuration has changed. Restarting webConfigurator.

Actions #1

Updated by Jim Pingle over 5 years ago

  • Category set to Web Interface
  • Status changed from New to Feedback
  • Assignee set to P L
  • Affected Version set to 2.5.0

There is not enough information here.

What exact steps are needed to reproduce the problem?

What was the state of the firewall when it started? Was it on HTTP? Was the GUI redirect option enabled? Any packages installed?

Actions #2

Updated by Jim Pingle about 5 years ago

  • Status changed from Feedback to Rejected

No feedback received.

Actions

Also available in: Atom PDF