Getting 'Not Found' error

Question

Getting 'Not Found' error

MarketingMandy opened this issue 4 years ago · comments

Hello

I've been using this for years and love it so thank you, but when I was checking something over, I realised my links now say 'Not Found' in the top left. I double checked and the original documents haven't been deleted, and I tried it again with another document and it isn't working for new ones either. I tried it on the Mac in both Chrome and Safari. Is there an issue? Sample link and screenshot: https://gdoc.pub/doc/1cY6qgS5ylRF8FDTD8zMr8wOI4o0Wwdtou3smB10gOp8#?usp=sharing

brandongoodwin02 · Answer 1 · Tue Dec 01 2020 22:18:11 GMT+0800 (China Standard Time)

I'm also getting the same "Not Found" response on many of my published pages. It's not on every page, but it is appearing on several of them.

Augustin Riedinger · Answer 2 · Wed Dec 02 2020 02:11:34 GMT+0800 (China Standard Time)

Hello Brandon, Apologies for this. I did make a small update which broke some documents. It is now fixed, you can check it out. Best, Augustin Riedinger

…

--- Want to hire a Web Freelancer? Checkout my Portfolio <http://augustin-riedinger.fr>. Looking for a place to work? Copass <https://copass.org/> offers flexible coworking at its best. No music inspiration? NovaTube <http://novatu.be> brings good music without interruption. Need to publish documents on the web easily? Try Google Doc Publisher <http://gdoc.pub>. Le mar. 1 déc. 2020 à 15:18, brandongoodwin02 <notifications@github.com> a écrit :

I'm also getting the same "Not Found" response on many of my published pages. It's not on every page, but it is appearing on several of them. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#51 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPA73C5A5N54NJASNFJVG3SST3LHANCNFSM4UI3665Q> .

MarketingMandy · Answer 3 · Wed Dec 02 2020 06:13:28 GMT+0800 (China Standard Time)

Thanks, Augustin - all my links are working now!

Glen Little · Answer 4 · Wed Dec 02 2020 11:53:24 GMT+0800 (China Standard Time)

@augnustin I'm still getting "Not Found". I've tried recreating the link, to no avail.

Augustin Riedinger · Answer 5 · Wed Dec 02 2020 16:50:15 GMT+0800 (China Standard Time)

@glittle Please send me the URL of your document at: https://www.augustin-riedinger.fr/contact

CarrieBush · Answer 6 · Fri Jan 13 2023 00:02:25 GMT+0800 (China Standard Time)

Our link is unreliable. We often get the "not found" message. Sometimes a refresh helps but not always. https://gdoc.pub/doc/e/2PACX-1vTQhVfS91iFmDK3gSLu9pE5fKkW1ThpvDKP1WZ-GuwxvuYIRDjBjqAQPV66WJSwTM-bbnZzoVQ0Zfd3 I am bummed because I love the way it looks when I can see it.

Augustin Riedinger · Answer 7 · Fri Jan 13 2023 00:28:49 GMT+0800 (China Standard Time)

I understand your concern, but unfortunately I hardly can fix anything if I can't reproduce the issue deterministically so I don't really see what I can do to help. :/

CarrieBush · Answer 8 · Fri Jan 13 2023 00:40:03 GMT+0800 (China Standard Time)

Thank you for your reply. I am in a currently in a meeting with 20 other instructional technology specialists throughout the state of Delaware and I shared the link with them. Everyone had trouble getting to it seamlessly. Weird. I’m glad it worked for you. Sent from iPhone

…

________________________________ From: Augustin Riedinger ***@***.***> Sent: Thursday, January 12, 2023 11:29:00 AM To: augnustin/google-docs-publisher ***@***.***> Cc: Bush Carolyn ***@***.***>; Comment ***@***.***> Subject: Re: [augnustin/google-docs-publisher] Getting 'Not Found' error (#51) I understand your concern, but unfortunately I hardly can fix anything if I can't reproduce the issue deterministically so I don't really see what I can do to help. :/ — Reply to this email directly, view it on GitHub<#51 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5G7ULK66MWVOY4YTD6NK3LWSAWMZANCNFSM4UI3665Q>. You are receiving this because you commented.Message ID: ***@***.***>

MandyHole · Answer 9 · Mon Jan 16 2023 22:23:47 GMT+0800 (China Standard Time)

Hi - just to say that we are getting this issue again from time to time as well. It doesn't work and then a few minutes later it does although nothing has changed. This has been the case for several colleagues across a few different documents...

Augustin Riedinger · Answer 10 · Tue Jan 17 2023 00:13:01 GMT+0800 (China Standard Time)

Hello all,
This feedback from multiple users interrogated me. I checked and it seems like there is an issue. I'm currently investigating and will let you know once it is fixed!
Apologies for the inconvenience.

Augustin Riedinger · Answer 11 · Tue Jan 17 2023 16:30:41 GMT+0800 (China Standard Time)

I just made an update on my server. It seems like it is working properly now. Do you guys confirm?

CarrieBush · Answer 12 · Tue Jan 17 2023 21:25:26 GMT+0800 (China Standard Time)

Thanks Augustin, So far so good from what I can tell. ☺ When your publishing tool didn’t work, I ended up embedding my Google Doc on a Google Site. So I now have alternate solution. Carrie Carrie Bush (she/her/hers) Digital Resource Teacher Caesar Rodney School District 302-697-2173 x129 https://tinyurl.com/bushandboulden From: Augustin Riedinger ***@***.*** Sent: Tuesday, January 17, 2023 3:31 AM To: augnustin/google-docs-publisher ***@***.***> Cc: Bush Carolyn ***@***.***>; Comment ***@***.***> Subject: Re: [augnustin/google-docs-publisher] Getting 'Not Found' error (#51) I just made an update on my server. It seems like it is working properly now. Do you guys confirm? — Reply to this email directly, view it on GitHub<#51 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5G7ULP3GUN5J2GBWW2DEKLWSZKDZANCNFSM4UI3665Q>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

MandyHole · Answer 13 · Wed Jan 18 2023 21:07:11 GMT+0800 (China Standard Time)

As far as I can tell, it's working, but I emailed a few colleagues to keep their eyes out. Thanks for fixing it - we will let you know if we see the error again.