Pfsense widget not working properly

[vk6xebec]

Description

I am unable to get pfSense and Unifi Controller Service to work properly

Pfsense:
I get an API error as follows

- Pfsense:
    icon: pfsense.svg
    href: "{{HOMEPAGE_VAR_PFSENSE_URL}}"
    description: Firewall
    siteMonitor: "{{HOMEPAGE_VAR_PFSENSE_URL}}" 
    widget:
        type: pfsense
        url: {{HOMEPAGE_VAR_PFSENSE_URL}}
        username: "{{HOMEPAGE_VAR_PFSENSE_USERNAME}}"
        password: "{{HOMEPAGE_VAR_PFSENSE_PWD}}"
        wan: pppoe0
        fields: ["load", "memory", "temp", "disk"]

I read from one of the other post that the WAN interface is pppoe0

These are my pfSense settings:

homepage version

0.8.9

Installation method

Docker

Configuration

- Pfsense:
        icon: pfsense.svg
        href: "{{HOMEPAGE_VAR_PFSENSE_URL}}"
        description: Firewall
        siteMonitor: "{{HOMEPAGE_VAR_PFSENSE_URL}}" 
        widget:
            type: pfsense
            url: {{HOMEPAGE_VAR_PFSENSE_URL}}
            username: "{{HOMEPAGE_VAR_PFSENSE_USERNAME}}"
            password: "{{HOMEPAGE_VAR_PFSENSE_PWD}}"
            wan: pppoe0
            fields: ["load", "memory", "temp", "disk"]

Container Logs

No response

Browser Logs

No response

Troubleshooting

1. Changed WAN interface to pppoe0 From: #2816
2. Installed curl in the container
3. Ran the curl command curl -u username:password https://pfsense.lan/api/v1/status/system

Got this error:

curl: (60) SSL certificate problem: self-signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

4. Ran command again with -k parameter
   curl -u -k username:password https://pfsense.lan/api/v1/status/system

Got this error code
{"status":"unauthorized","code":401,"return":3,"message":"Authentication failed","data":[]}

Looks like it has a problem with my self signed certificate.

5. I tried to change from https to http in the pfsense GUI settings, but the homepage widget timed out.

Any ideas?

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided, it seems that there are a couple of issues that need to be addressed:

1. Self-Signed Certificate Issue: The error message from the curl command indicates that the self-signed certificate is not trusted. Since homepage accepts self-signed certificates, this should not be an issue for the widget itself. However, when using curl from the command line, you need to include the -k or --insecure option to bypass the certificate verification, as you did in your troubleshooting step 4.

2. Authentication Failure: The {"status":"unauthorized","code":401,"return":3,"message":"Authentication failed","data":[]} response indicates that the credentials provided are not correct or the user does not have the necessary permissions. Ensure that the username and password are correct and that the user has the required permissions to access the pfSense API.

3. WAN Interface Configuration: The WAN interface should be set to the correct identifier as used by pfSense. If pppoe0 is the correct interface identifier as per your pfSense settings, then it should be correctly set in the widget configuration. However, if the interface identifier is different, you will need to update the wan parameter in your widget configuration to match the correct identifier.

4. HTTP vs HTTPS: If you are switching from HTTPS to HTTP in the pfSense GUI settings, make sure to update the widget url in the homepage configuration to use http instead of https. Also, ensure that pfSense is configured to allow HTTP connections if you choose to use HTTP.

5. Network Connectivity: Verify that the homepage container can reach the pfSense API. You can do this by executing a ping command from within the homepage container to the pfSense host.

Here are the steps you can take to resolve the issues:

• Double-check the username and password for the pfSense API and ensure that the user has the necessary API permissions.
• If you continue to use HTTPS, ensure that the homepage widget is configured to accept the self-signed certificate.
• If you switch to HTTP, update the widget url to use http and ensure pfSense allows HTTP connections.
• Verify network connectivity between the homepage container and the pfSense host.

If you have followed these steps and are still encountering issues, please provide the exact error message you are seeing in the homepage widget, and ensure that the pfSense API is accessible from the homepage container.

This comment was generated by Glime.

[vk6xebec]

#3 Yes the username and password is correct. It does have the permissions set
#4. I have switched the URL from https to http and it does not work
#5 . Ping to pfsense works

[P0pzi]

Identical issue here - Have even goen as far as turning off all auto-lockout features in PFSense and any HTTP Referrer settings, still not able to talk to it, despite being able to do so just fine via curl.

I also note that Homepage's logs fail to log the error correctly (undefined).

Taking a very quick look through the code, it looks like we're encoding the passwords in base64, which I'm not sure the pfsense package is expecting.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.