Project

General

Profile

Actions
Copy link

Feature #8578

closed

/var/unbound/test/unbound_server.pem: No such file or directory

Added by Neil Esperon almost 6 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/18/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

We cant save settings in DNS Resolver, we cant disable it either. We cant do browsing because of this. Can you help us?

Files

pfsense_issue.PNG (61.5 KB) pfsense_issue.PNG Screenshots Neil Esperon, 06/18/2018 09:24 PM
Actions
Copy link
 #1

Updated by Jim Pingle almost 6 years ago

  • Status changed from New to Rejected
  • Priority changed from Urgent to Normal

There is not enough information here for a bug report, and this is not a support or discussion platform.

Please post on the forum at https://forum.netgate.com or on the pfSense subreddit at https://reddit.com/r/pfSense/ to discuss your problem.

Actions
Copy link
 #2

Updated by Vincent Bentley over 5 years ago

I changed the IP address of my OPT3 interface today and now have the same error. Unbound was already listening on this interface and has been working just fine since Unbound Resolver was first added to pfSense some years ago. The service will not start since the IP address change today.

I manually created a proper PEM file as /var/unbound/test/unbound_server.pem but it is automatically deleted by some part of pfSense and cannot be found when trying to restart the service.

I do not use DDNS.

I use permanent DHCP leases.

Actions
Copy link
 #3

Updated by Vincent Bentley over 5 years ago

I deselected OPT3 (the interface with the changed IP address) from Unbound listening but it makes no difference. When tyring to save settings the unbound_server.pem error is displayed and the service will not start.

I am going to do a backup/restore of config.xml to see if that is a workaround to get Unbound started. The config.xml looks OK and I can't see any problems comparing it to a previous backup apart from the IP address changes so I am hopeful that this will work.

Actions
Copy link
 #4

Updated by Vincent Bentley over 5 years ago

Cannot restore 'DNS Resolver' or 'All' from browser, both result in NGINX error (500 I think, I didn't write it down).

I toggled on and off pfBlockerNG, saving the configuration between toggling and this created a recent configuration change to restore from using the console menu item 15.

Using Console menu item 15, I selected backup number 1, restored it, rebooted, and Unbound is running again. This is a workaround that works for me.

Actions
Copy link

Also available in: Atom PDF