Skip to content
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

Custom Domain Issue #1699

Closed
tomcooperandco opened this issue May 4, 2016 · 1 comment
Closed

Custom Domain Issue #1699

tomcooperandco opened this issue May 4, 2016 · 1 comment

Comments

@tomcooperandco
Copy link

tomcooperandco commented May 4, 2016

Hi,

Not sure if I've found a bug or having issues with a lack of documentation. Either way, I have a working Parse Server install in Heroku using the Heroku domain. As soon as I attempt to apply a custom domain, I have issues as reported in more detail here:

http://stackoverflow.com/questions/37015329/parse-server-custom-domain-on-heroku

(None of the edits in the past month since my last pull request are of consequence to this issue).

  • [y] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

parse-server-example running in Heroku

Steps to reproduce

http://stackoverflow.com/questions/37015329/parse-server-custom-domain-on-heroku

Logs/Trace

N/A

@hramos
Copy link
Contributor

hramos commented May 6, 2016

Closing as this was already posted on Stack Overflow. If you want this to be addressed here instead, please include all the necessary details to start an investigation in the issue itself.

You may use Server Fault for questions about managing Parse Server.

For code-level and/or implementation-related questions or technical support, please refer to Stack Overflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants