Closed baghdadbrian closed 7 years ago
SSL certificate expired on the api subdomain.
HTTP POST https://api.storymaker.org/api/oauth2/access_token 01-26 20:50:46.283 19517 20357 D Retrofit: ---- ERROR https://api.storymaker.org/api/oauth2/access_token
01-26 20:50:46.286 19517 20357 D Retrofit: Caused by: java.security.cert.CertificateExpiredException: Certificate expired at Fri Dec 23 15:57:00 EST 2016 (compared to Thu Jan 26 20:50:46 EST 2017)
wget https://api.storymaker.org/api/oauth2/access_token --2017-01-26 20:52:38-- https://api.storymaker.org/api/oauth2/access_token Resolving api.storymaker.org (api.storymaker.org)... 52.8.64.148 Connecting to api.storymaker.org (api.storymaker.org)|52.8.64.148|:443... connected. ERROR: cannot verify api.storymaker.org's certificate, issued by ‘/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3’: Issued certificate has expired.
Done.
Generating key (2048 bits): /etc/letsencrypt/keys/0002_key-certbot.pem Creating CSR: /etc/letsencrypt/csr/0002_csr-certbot.pem
Congratulations, all renewals succeeded. The following certs have been renewed: /etc/letsencrypt/live/api.storymaker.org/fullchain.pem (success)
Confirmed, works as expected
On Thu, Jan 26, 2017, 18:52 Nathan Freitas notifications@github.com wrote:
Done.
Generating key (2048 bits): /etc/letsencrypt/keys/0002_key-certbot.pem Creating CSR: /etc/letsencrypt/csr/0002_csr-certbot.pem
new certificate deployed without reload, fullchain is /etc/letsencrypt/live/api.storymaker.org/fullchain.pem
Congratulations, all renewals succeeded. The following certs have been renewed: /etc/letsencrypt/live/api.storymaker.org/fullchain.pem (success)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/StoryMaker/storymaker/issues/182#issuecomment-275577543, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLBzYgb2WjorbbDcO0HFtiLTIHZ0Jgcks5rWVvOgaJpZM4LvRRs .
That said, the publishing process doesn't give you any link to the post on storymaker.org or youtube or anywhere. It is really confusing and a step back from storymaker v1 simpler publishing experience.
@vitriolix Is this some kind of bug, or was there meant to be more implemented.
I still see an option to "view online" after uploading to youtube.
you don't?
On Thu, Jan 26, 2017 at 7:02 PM, Nathan Freitas notifications@github.com wrote:
That said, the publishing process doesn't give you any link to the post on storymaker.org or youtube or anywhere. It is really confusing and a step back from storymaker v1 simpler publishing experience.
@vitriolix https://github.com/vitriolix Is this some kind of bug, or was there meant to be more implemented.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/StoryMaker/storymaker/issues/182#issuecomment-275578703, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLBzZEWDv9xItjKeYwMQc7QhI8fxsJNks5rWV45gaJpZM4LvRRs .
--
Brian Conley
Co-founder, Small World News
m: 646.285.2046
Skype: brianjoelconley
I don't see that. Can you post a screenshot?
This didn't come through from the email thread, not sure why:
Hmm, not seeing that popup here, but will try again. Thanks!
This also relates to the need for improved background publishing and notifications, because it is easy to miss a popup dialog like that.
logging in on the website works as expected. logging in via the app returns "Login error."
This does not seem to be a connectivity or location issue, it has been reproduced in ukraine and portland oregon. though a similar issue has been reported previously, I could not recreate it in earlier builds of the app. today I can no longer log into the storymaker.org site from the storymaker app. on previous recent builds it was possible.