BUG: Swagger UI uses incorrect server URL (52123) while backend runs on 8000

[prabalpatkar558412-collab]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Description

When running the PictoPy backend locally using uvicorn on port 8000,
the Swagger UI (/docs) sends API requests to http://localhost:52123,
which causes all API calls to fail with "Failed to fetch".

Steps to Reproduce

1. Run backend using: python -m uvicorn main:app --reload
2. Open http://127.0.0.1:8000/health → works correctly
3. Open http://127.0.0.1:8000/docs
4. Try any endpoint (e.g. POST /folders/add-folder)
5. The request is sent to http://localhost:52123 and fails

Expected Behavior

Swagger UI should use the same server URL/port as the running backend (8000).

Actual Behavior

Swagger UI uses a hardcoded server URL pointing to port 52123.

Additional Context

Backend is running correctly on port 8000.
I would like to work on fixing this issue.

Record

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[prabalpatkar558412-collab]

@rahulharpal1603 Hi maintainers 👋
I have reproduced this issue locally and would like to work on fixing it.
Please assign this issue to me. Thanks!

[skyforge-glitch]

@prabalpatkar558412-collab

Clarification on expected backend ports

Thanks for reporting this.

This behavior is expected with the current local development setup. PictoPy’s backend is designed to run on port 52123 (and the sync microservice on 52124) during local development. The Swagger UI (/docs) is configured to use this expected backend port.

In the reported steps, the backend is started using:

python -m uvicorn main:app --reload

which defaults to port 8000. This creates a port mismatch:

• Backend is running on 8000
• Swagger UI is configured to send requests to 52123

As a result, Swagger requests fail with “Failed to fetch”.

How to run the backend correctly

To avoid this issue, the backend should be started on the expected port:

uvicorn main:app --host 127.0.0.1 --port 52123

This aligns the runtime port with the Swagger configuration, and API calls from /docs should work as intended.

Note on setup documentation

For local development, the expected ports and startup commands are already documented in the Manual Setup Guide and Script Setup Guide. Following those setup steps ensures the backend and sync services run on the correct ports (52123 and 52124), which keeps the Swagger UI and other components in sync.

If the backend is started outside of those documented flows (for example, using the default uvicorn command on port 8000), the port mismatch can lead to the behavior described above.

Happy to help clarify the documentation further if needed.

[prabalpatkar558412-collab]

Thanks for the clarification!

I understand now that the backend is expected to run on port 52123.
As a new contributor, I ran uvicorn with the default port (8000) and got confused.

I think this could easily happen to other new contributors as well.
Would it be okay if I submit a small documentation PR to clearly highlight
the required backend ports and the correct uvicorn command?

[skyforge-glitch]

Thanks for the clarification!

I understand now that the backend is expected to run on port 52123. As a new contributor, I ran uvicorn with the default port (8000) and got confused.

I think this could easily happen to other new contributors as well. Would it be okay if I submit a small documentation PR to clearly highlight the required backend ports and the correct uvicorn command?

@prabalpatkar558412-collab
The required backend ports and startup commands are already documented in the Manual and Script Setup guides.
I agree this can still confuse new contributors though, we could make this more prominent if maintainers think it’s worth highlighting.

[prabalpatkar558412-collab]

Thanks for the clarification!

That makes sense — I see the information is already present in the setup guides.

To keep it minimal, I was thinking of:

• Adding a short “⚠️ Default backend port” note near the backend startup instructions
• Explicitly mentioning that running uvicorn without --port 52123 will cause Swagger (/docs) requests to fail

No behavior or code changes, just a small visibility improvement for first-time contributors.

If that sounds reasonable, I can open a small docs PR. Please let me know 👍