Service reports: filter: denying api access: failed to identify process

[3n1gmus]

What happened:
Note: Running Arch Linux, Installed via AUR package. https://aur.archlinux.org/packages/portmaster-stub-bin
Portmaster GUI not connecting to service. Service reporting API not authorized.

Running 'systemctl status portmaster', reports

● portmaster.service - Portmaster by Safing
Loaded: loaded (/etc/systemd/system/portmaster.service; enabled; preset: disabled)
Active: active (running) since Wed 2023-09-13 09:33:36 MDT; 2h 31min ago
Docs: https://safing.io
https://docs.safing.io
Main PID: 834 (portmaster-star)
Tasks: 33 (limit: 37387)
Memory: 1.3G
CPU: 50.244s
CGroup: /system.slice/portmaster.service
├─ 834 /opt/safing/portmaster/portmaster-start --data /opt/safing/portmaster core --
└─1003 /opt/safing/portmaster/updates/linux_amd64/core/portmaster-core_v1-4-5 --data /opt/safing/portmaster

Sep 13 12:04:32 Faith portmaster-start[834]: 230913 12:04:32.338 rewall/api:200 ▶ WARN 874 filter: denying api access: failed to identify process
Sep 13 12:04:32 Faith portmaster-start[834]: 230913 12:04:32.838 rewall/api:200 ▶ WARN 876 filter: denying api access: failed to identify process
Sep 13 12:04:33 Faith portmaster-start[834]: 230913 12:04:33.339 rewall/api:200 ▶ WARN 878 filter: denying api access: failed to identify process
Sep 13 12:04:33 Faith portmaster-start[834]: 230913 12:04:33.840 entication:291 ▶ WARN 880 api: denying api access from 127.0.0.1:59098
Sep 13 12:04:34 Faith portmaster-start[834]: 230913 12:04:34.852 rewall/api:200 ▶ WARN 882 filter: denying api access: failed to identify process
Sep 13 12:04:35 Faith portmaster-start[834]: 230913 12:04:35.353 rewall/api:200 ▶ WARN 884 filter: denying api access: failed to identify process
Sep 13 12:04:35 Faith portmaster-start[834]: 230913 12:04:35.854 rewall/api:200 ▶ WARN 886 filter: denying api access: failed to identify process
Sep 13 12:04:36 Faith portmaster-start[834]: 230913 12:04:36.355 rewall/api:200 ▶ WARN 888 filter: denying api access: failed to identify process
Sep 13 12:04:36 Faith portmaster-start[834]: 230913 12:04:36.856 rewall/api:200 ▶ WARN 890 filter: denying api access: failed to identify process
Sep 13 12:04:37 Faith portmaster-start[834]: 230913 12:04:37.356 entication:291 ▶ WARN 892 api: denying api access from 127.0.0.1:59100

There was nothing notable in the logs, but I can send them if needed.

What did you expect to happen?:
Postmaster UI to connect to service and to be able to utilize portmaster

How did you reproduce it?:
Happens directly after installation.

Debug Information:

[github-actions]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[dhaavi]

Hey @3n1gmus, thanks for reporting.

How are you opening the UI?
Can you start the notifier and check if it works? (There should be an entry in your system)

[3n1gmus]

How are you opening the UI?
I am opening it from the tray icon and/or from my KDE menu. The interface opens but only reports connecting to portmaster.

Can you start the notifier and check if it works? (There should be an entry in your system)
Apologies, you will need to supply the steps or guidance for this. Quick search on the Safing wiki did not turn this up other then that there is a notifer. If you are talking about the tray icon itself, it constantly displays a red dot, and the drop down shows Open app, 'loading...' (three times), Rate your network (greyed out), close tray notifier, and shutdown portmaster.

[3n1gmus]

Touching base on this as I have not received information that resolves the issue.

[dhaavi]

Thanks for the bump.

This is super weird. You can try to enable the developer mode for now - this should work, but any process (but not random websites) could make changes your Portmaster settings. So we should not use this extensively.

Our support bot made this guide for you:

---

To enable the development mode via the config file on Windows, you need to modify the config.json file located at C:\ProgramData\Safing\Portmaster\config.json.

Here is a template for the config.json file where the development mode is enabled:

{
  "core": {
    "devMode": true
  }
}

In this JSON structure, "devMode": true enables the development mode.

Please note that you should validate the JSON before using your config to avoid any syntax errors.

For more details, you can refer to the Portmaster documentation (https://docs.safing.io/portmaster/settings#core/devMode).