github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-11 16:31:19 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #1935] API commands not showing up #2046

New Issue
Closed
opened 2026-04-16 09:00:09 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-16 09:00:09 -05:00
Owner
Copy Link

Originally created by @PottiMc on GitHub (Nov 28, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1935

Describe the Bug

When I want to debug settings or get IDs in the Pangolin API docs the black window with the code and the commands does not show up. So I can't get any information I want.

What I did to debug:

  • Generated a universal API key and a single Site API key -> no difference
  • Tried with Authorization in the API and without -> no difference
  • Tried different browser (Chrome, Edge, Firefox) -> no difference
  • Deleted cache in Chrome and Firefox -> no difference
  • Updated Pangolin v1.12.1 to 1.12.2 -> no difference
  • Restarted all docker containers (during the update process) -> no difference
  • Checked the Pangolin docs for the integration API and double checked with my config -> All according to the docs

The API itself is working. I use a Rule Updater script which is working fine.

Image

Environment

Debian 12 - Docker 28.3.3

To Reproduce

Open the API url -> Authorize or don't -> Choose GET/orgs for example (doesn't matter which one -> Click "Try it out" -> Click "Execute" -> Just a very short "Loading" is apperaing beneath the button, but it disappears and nothing changed.

Expected Behavior

I would like the black and white API answer like expected

Originally created by @PottiMc on GitHub (Nov 28, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1935 ### Describe the Bug When I want to debug settings or get IDs in the Pangolin API docs the black window with the code and the commands does not show up. So I can't get any information I want. What I did to debug: - Generated a universal API key and a single Site API key -> no difference - Tried with Authorization in the API and without -> no difference - Tried different browser (Chrome, Edge, Firefox) -> no difference - Deleted cache in Chrome and Firefox -> no difference - Updated Pangolin v1.12.1 to 1.12.2 -> no difference - Restarted all docker containers (during the update process) -> no difference - Checked the Pangolin docs for the integration API and double checked with my config -> All according to the docs The API itself is working. I use a Rule Updater script which is working fine. <img width="1536" height="552" alt="Image" src="https://github.com/user-attachments/assets/f767a311-1d27-471e-80b1-e1eae2172a99" /> ### Environment Debian 12 - Docker 28.3.3 ### To Reproduce Open the API url -> Authorize or don't -> Choose GET/orgs for example (doesn't matter which one -> Click "Try it out" -> Click "Execute" -> Just a very short "Loading" is apperaing beneath the button, but it disappears and nothing changed. ### Expected Behavior I would like the black and white API answer like expected
GiteaMirror added the stale label 2026-04-16 09:00:09 -05:00
GiteaMirror commented 2026-04-16 09:00:11 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Nov 29, 2025):

This would be a swagger issue and I think it is usually caused by CORS
or an other reason preventing the API request from going through. I
would like the swagger team to provide a little more feedback in the gui
about this!

Can you open the dev tools in the browser and make the request and see
why the API request is failing?

<!-- gh-comment-id:3591761590 --> @oschwartz10612 commented on GitHub (Nov 29, 2025): This would be a swagger issue and I think it is usually caused by CORS or an other reason preventing the API request from going through. I would like the swagger team to provide a little more feedback in the gui about this! Can you open the dev tools in the browser and make the request and see why the API request is failing?
GiteaMirror commented 2026-04-16 09:00:11 -05:00
Author
Owner
Copy Link

@Kacper1263 commented on GitHub (Dec 2, 2025):

hi @oschwartz10612, I think I have the same problem. API is working, in dev tools I can see request and proper response but Swagger is not showing it.

Image Image

All adblocks etc. are disabled, looks like a bug in Swagger

<!-- gh-comment-id:3600834882 --> @Kacper1263 commented on GitHub (Dec 2, 2025): hi @oschwartz10612, I think I have the same problem. API is working, in dev tools I can see request and proper response but Swagger is not showing it. <img width="1911" height="839" alt="Image" src="https://github.com/user-attachments/assets/cbcaf630-20ad-483c-abd0-76bb66375bd1" /> <img width="1916" height="915" alt="Image" src="https://github.com/user-attachments/assets/20b9097c-e1d3-488e-9f5a-9f7ed498ab12" /> All adblocks etc. are disabled, looks like a bug in Swagger
GiteaMirror commented 2026-04-16 09:00:12 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 2, 2025):

Hum must be because you are clearly getting a response to the request. Very strange! Will try to update swagger for the next release to see if it fixes it.

<!-- gh-comment-id:3602486197 --> @oschwartz10612 commented on GitHub (Dec 2, 2025): Hum must be because you are clearly getting a response to the request. Very strange! Will try to update swagger for the next release to see if it fixes it.
GiteaMirror commented 2026-04-16 09:00:13 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 17, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3663028736 --> @github-actions[bot] commented on GitHub (Dec 17, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-16 09:00:13 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 31, 2025):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:3700919786 --> @github-actions[bot] commented on GitHub (Dec 31, 2025): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
GiteaMirror commented 2026-04-16 09:00:14 -05:00
Author
Owner
Copy Link

@PottiMc commented on GitHub (Feb 25, 2026):

@oschwartz10612 Just a short reminder to bump Swagger. API window is still not showing up.

<!-- gh-comment-id:3961944570 --> @PottiMc commented on GitHub (Feb 25, 2026): @oschwartz10612 Just a short reminder to bump Swagger. API window is still not showing up.
GiteaMirror commented 2026-04-16 09:00:16 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Feb 25, 2026):

I dont think swagger-ui-express is updated past 5.0.1... Maybe we need
to find a difference solution?

<!-- gh-comment-id:3962318366 --> @oschwartz10612 commented on GitHub (Feb 25, 2026): I dont think swagger-ui-express is updated past 5.0.1... Maybe we need to find a difference solution?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#2046
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?