interledger / interledger-website

🙅 Previous version of the interledger.org website

Home Page:https://interledger.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Interledger White Paper page has a page not found code

jessiehennion828 opened this issue · comments

@jessiehennion828
Can you describe the steps you took to upload this PDF in the CMS so that we can help troubleshoot?

Thanks!

I am verifying with @jessiehennion828 but I think the PDF was on the site prior to DNS switch. I checked on the old repo and it was simply a file at the root. Not sure right approach but we could create a /files/ folder in Cloudcannon and upload it there. I'm just a big fan of keeping root clean. @tbeck thoughts?

Here is the original https://github.com/interledger/interledger.github.io/blob/master/interledger.pdf

@tbeck I uploaded through CMS it went to root. But I get 404 if I try interledger.org/interledger.pdf

@mccamon I was able to upload to both the root and uploads folder in the CMS on staging. Do either/both of these links work as the intent?

https://frank-beach.cloudvent.net/uploads/interledger.pdf

https://frank-beach.cloudvent.net/interledger.pdf

@mccamon - If you are okay with this, I would suggest placing the file in the uploads directory and keep the root folder clean. In the meantime, we can also add a 301 redirect to account for any existing instances of the link to the https://interledger.org/insterledger.pdf

Let me know if this is okay and we will push as part of our EOD merge.

Thanks!

Approved. It is in root and in uploads. 301 is good because it's a legacy link from old site. 301s managed in Cloudflare?

Hi @mccamon - 301 can be managed in Cloudcannon using the 301.txt file. Here is a direct link: https://app.cloudcannon.com/32080/editor#sites/88070/browser/src:/browser/src/301.txt

That being said... it looks like there is some issue with the domain. We have submitted a ticket with Cloudcannon to see if they have any ideas, but we may also need to look at the Cloudflare settings to see if something is in place that is preventing that url from resolving. We should see if we can get credentials from Briana.

Reporting that neither location is working.

https://interledger.org/src/uploads/interledger.pdf << 404
https://interledger.org/interledger.pdf << 404

BTW @tbeck it looks like you 301 with Cloudcannon https://docs.cloudcannon.com/hosting/general/301-redirects/ But until I get the /uploads/ link to work that still doesn't fully solve this issue

Hi @mccamon
In this build the "src" acts as the root. So the link would be: https://interledger.org/uploads/interledger.pdf
This appears to be working on this end.

We will continue to troubleshoot the redirect though. The Cloudcannon team thought that there may be a configuration setting in the Cloudflare account , however we will need access from Briana to explore that possibility further.

Yes, @tbeck that link did work yesterday... now https://interledger.org/uploads/interledger.pdf resolves to 404. I would try the 301-redirect feature in Cloudcannon but I don't have a link that works as a patch. I also opened a ticket with Cloudcannon.

Lastly I did look aroudn their doc this morning and I can't get to the Site > Settings - maybe there's setting there that impact this sort of file request. (since all the links of files in uploads are oviscaped like when I right mouse click on Briana's image and the link is not simply /uploads/briana-marbury.jpg)

@mccamon - Let's connect offline and I can run through some of the details you outlined above. Cloudcannon does optimize assets before pushing to their CDN and I think that this is what you are referring to regarding the path/filename inconsistencies.

Here is an outline of what we have tried so far for reference:

  • We have placed the pdf in the root of the source folder
  • We moved the file to the uploads directory and added a redirect in 301.txt
  • Both the direct file load and redirect work on a staging url, but fail with the interledger.org domain.
  • Explored the Cloudflare settings to see if there may be anything out of the ordinary there but nothing stood out. This may need further digging, but feels like a long shot.
  • We renamed the PDF and tested in the root. It works as expected: https://interledger.org/test.pdf

Just as a precaution, can you confirm that you have cleared your browser cache or are using an incognito window before testing any of the links?

Thanks!

@mccamon / @bmarbury - Marking this complete. Purging the cache in Cloudflare solved the issue.