-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fix infinite redirect and get site back online #151
Comments
@todrobbins do you think this is a configuration problem in Heroku? |
Could be... Do you have Heroku access now? Also, could be a DNS issue maybe? |
No, Heroku has changed its terms of use recently and I've decided to delete my account because of that. I have already started working on converting the site to a statically generated Jekyll site (issue #154 on branch jekyll-site) so we can host it on Github Pages instead. Once it is done we will still need to change the DNS to point it to Github Pages. |
Sounds good! I'll take a look at the new branch. DNS changes will need to come from @okfn/devops @okfn/staff |
I can't find any rule or setting in Heroku or Cloudflare that might cause the redirects. Maybe it's a SSL issue? In any case happy to change the DNS to point to Github pages when that's ready |
Hi @amercader! With PR #158 we're ready to move on to Github Pages. I think we should change the DNS already, the site on Heroku has been offline for a few months anyway. |
In addition to the DNS change, to make Github Pages work someone would need to configure it in the "Settings" tab of this repository, which I do not have access to. Do you, @todrobbins? |
@augusto-herrmann you should be an admin for this repo now |
Thanks, @amercader! I'm in a hurry right now but should work in getting the site back online as soon as I can. |
Right now when accessing the site the user gets infinite redirects, which make it inaccessible.
We should fix the site deployment ASAP.
Judging by the headers it could be some kind of problem with CloudFlare.
The text was updated successfully, but these errors were encountered: