-
-
Notifications
You must be signed in to change notification settings - Fork 619
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
Issue with proxy #1014
Comments
It's a known limitation that a Proxy is not supported. Why not setup the custom domain directly in Heroku |
Please add support to set more hostnames separated with |
hey @masteradit and @anondev-sudo can you have a look at this PR #1069 ? If you're still having this issue, please try using |
I'm going to close this one as the latest version greatly simplify this by using relative path to resources. Just remember to set Reopen if the problem persist even after updating to |
I have hosted Fider on Heroku and I have set up a proxy on Netlify to use a custom domain with SSL (which Netlify automatically provides). However, when I go to the website, it gives me a
PAGE NOT FOUND
error.Steps to reproduce:
something.herokuapp.com
as the domain.Netlify.toml
:HOST_DOMAIN
in Config Vars on Heroku and put the value asfider-testing.domain.tld
which is the custom domain added in Netlify.fider-testing.domain.tld
.Error shown:
Browser Console:
I can't see any errors in Heroku logs, so I feel it isn't something on Heroku's end.
The text was updated successfully, but these errors were encountered: