-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post request Failure with Nginx reverse proxy #2178
Comments
@SgtPooki looks like there is a bug in the loadHttpClientModule: () => create(apiAddress),
This might fix this, however this would require a setup like @akimoto72738 has to test. |
@akimoto72738 you should be able to do However, this will be changing when I fix #2176 shortly, and you'll need to do |
@whizzzkid I'm going to be getting rid of ipfs-provider since it's another one of those very old and unmaintained packages. |
Yes, I felt so, |
Hi @SgtPooki , I have listed most of the fields in localStorage for your investigation, I dont know what value for apiOpts, I just copy and paste and here is my api setting in webui interface @whizzzkid thanks
|
@akimoto72738 currently, the Ideally, we should be able to infer the PS.. the latest ipfs-webui supports the |
One more thing. your original question was
You should run the following in your browser console: you should be able to verify the same functionality at explore.ipld.io (which is a web version of the explore page) |
I use Nginx as a reverse proxy for the IPFS API interface with the domain name api.mydomain.com, and it works well. However, the EXPLORE page(only) is not functioning properly. I have identified that the browser still use 127.0.0.1:5001 for POST requests in this page. How should I configure it to make the browser use https://api.mydomain.com/ for POST requests?
Here is my config about api
"Addresses": {
"API": "/dns4/api.mydomain.com/tcp/5001",
"Announce": [],
"AppendAnnounce": [],
"Gateway": [
"/dns4/gateway.mydomain.com/tcp/443",
"/ip4/0.0.0.0/tcp/8080"
],
other page is normal
updated:
I return the webui version to [v3.0.0],then the problem resolved XD (before is 4.1.1 latest)
The text was updated successfully, but these errors were encountered: