Paragraph

@paragraph my custom domain https://powerlaw.systems is not pointing to my blog anymore. The page I am getting is the Paragraph website. Could you take a look?

Where writers share, grow, and get paid — one post at a time.

https://powerlaw.systems/memo-w08-feb-2025

Gives 404 in the browser.

This is the alt account of Sister Hazel. Writings at https://powerlaw.systems. Curating https://protocol-particles.github.io.

I'm having trouble recreating this issue — when I open your link, either by clicking the link from Farcaster or copying & pasting it into the browser, it takes me to your publication.

I may be misunderstanding your request — did you want the reader to be directed to an external, non-Paragraph hosted site?

This is what I see in Chrome on MacOS. Funny enough, on Safari I see my blog as expected. Android mobile phone is also ok. Only Chrome is broken.

This error shows in Chrome, but not in Safari. Don't know whether that is actually relevant.

This is my Chrome version in which I see the issue.

This is all I see when I try to read my blog from the cast above in Chrome on Laptop. Not sure whether this is Paragraph or Warpcast related.

Very much appreciate the details — we're looking into & hope to have a fix up soon.

Thank you for the update. I cleared my cookies and the issue appears to be fixed on my end.

Just now I need to login again to Paragraph and I don't recall which wallet I used for that. Can you tell me how I find this out again?

I logged in with a wallet that I thought I have used, but my posts weren't there. So I guess it is another one.

I think this is related to a previous bug with the recent frames update. We fixed the bug, but in some edge cases, the cookie was carried over.

If you clear your cookies, it should work. Or, to your point above, if you try in a different browser, it should work.

Sorry for the trouble!

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 

The situation appears unchanged on my end. I do not see my blog on my domain in Chrome.

@colin pushed what we hope to be a fix here — mind checking on your end and letting us know if you continue to have any issues?