lllyasviel / lllyasviel/FramePack
Unable to run behind reverse proxy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.3k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I run my services behind a protected reverse proxy, but it seems that it causes issues with Framepack, is there a way to fix this?
```py
Traceback (most recent call last):
File "/config/workspace/miniconda3/envs/framepack/lib/python3.10/site-packages/gradio/queueing.py", line 616, in process_events
api_route_path = route_utils.get_api_call_path(request=body.request)
File "/config/workspace/miniconda3/envs/framepack/lib/python3.10/site-packages/gradio/route_utils.py", line 397, in get_api_call_path
raise ValueError(f"Request url '{root_url}' has an unkown api call pattern.")
ValueError: Request url 'https://framepack.example.com' has an unkown api call pattern.
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Gradio traceback in queueing.py and route_utils.py, especially get_api_call_path, and reproduce the request through the protected reverse proxy using the reported URL. The issue is resolved when FramePack accepts the proxied request without the unknown API call pattern error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100