Pi-hole Widget CORS about homepage HOT 10 CLOSED

I've added the option to proxy the API requests,

widget:
  type: pihole
  url: http://pi.hole
  proxy: true # this will enable the CORS proxy

from homepage.

I'm getting follow error when I have proxy on or off.
The Same Origin Policy disallows reading the remote resource at http://10.10.10.10/admin/api.php. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.

config

    - Pihole:
        icon: pihole.png
        href: http://10.10.10.10/admin
        descriptition: Pihole Server
        widget:
          type: pihole
          url: http://10.10.10.10
          #proxy: true # Optional, only use if it doesn't work otherwise

UPDATE: Sorry, Production outage. Brain not working. Fix words

from homepage.

I've added the option to proxy the API requests,

widget:
  type: pihole
  url: http://pi.hole
  proxy: true # this will enable the CORS proxy

Thanks for looking at this so quickly. I've pulled the latest version and am not getting an internal server error when I try and load the page. (This is with or without the proxy:true line).

The container logs are giving the following information:

TypeError: handler is not a function
    at Server.<anonymous> (/app/server.js:19:11)
    at Server.emit (node:events:513:28)
    at parserOnIncoming (node:_http_server:980:12)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)

from homepage.

It was an unrelated bug, which has been fixed now.

from homepage.

It was an unrelated bug, which has been fixed now.

Thanks!

from homepage.

I'm still getting the API error. I have tried to target the IP and port directly (http://192.168.1.254/admin) and I have tried with the proxy setting set to true and still nothing.

from homepage.

What version of PiHole are you running?

from homepage.

What version of PiHole are you running?

v5.18.1

from homepage.

I'm getting a similar error with the SAB API call:

TypeError [ERR_INVALID_URL]: Invalid URL at new NodeError (node:internal/errors:393:5) at URL.onParseError (node:internal/url:564:9) at new URL (node:internal/url:644:5) at genericProxyHandler (/app/.next/server/pages/api/services/proxy.js:379:19) at async Object.apiResolver (/app/node_modules/.pnpm/[email protected]_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/server/api-utils/node.js:366:9) at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected]_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/server/next-server.js:469:9) at async Object.fn (/app/node_modules/.pnpm/[email protected]_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/server/next-server.js:719:37) at async Router.execute (/app/node_modules/.pnpm/[email protected]_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/server/router.js:247:36) at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected]_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/server/base-server.js:346:29) at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected]_biqbaboplfbrettd7655fr4n2y/node_modules/next/dist/server/base-server.js:284:20) { input: 'undefined/api/?apikey=d164c44b2bbffd08c7f731990e25fc2d&output=json&mode=queue', code: 'ERR_INVALID_URL' }

from homepage.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.

from homepage.