search

AstroProfundis / embrr

A web client of Twitter, forked from embr, with better compatibility and functionality.
GNU General Public License v3.0
40 stars 7 forks source link

Ooops, an unknown error occured. Please go back or sign in again.是怎么回事？ #50

Closed licess closed 10 years ago

licess commented 10 years ago

你好， 登陆时报如下信息： Ooops, an unknown error occured. Please go back or sign in again. 一直在用没什么问题，今天突然登陆不上，重新git pull了新版的还是一样的错误 换了一个空间试了试还是一样的错误

AstroProfundis commented 10 years ago

这个问题一般都是无法连接到 twitter 造成的，如果确认主机本身能够访问 api.twitter.com 的话有可能是官网宕机。

shadowglen commented 10 years ago

啊... 也有可能是config没填对

AstroProfundis commented 10 years ago

话说最近观察到了若干次 http_code 为 0 或者 200 跳到错误页面的...

ghost commented 10 years ago

Also see same error. On Jan 31, 2014 11:36 AM, "Allen Zhong" notifications@github.com wrote:

话说最近观察到了若干次 http_code 为 0 或者 200 跳到错误页面的...

— Reply to this email directly or view it on GitHubhttps://github.com/AstroProfundis/embrr/issues/50#issuecomment-33759303 .

shadowglen commented 10 years ago

如果是近两天的话 可能是twitter服务器本身的问题 我在官网也偶尔看到internal server error

Sent from my Windows Phone

From: Jon Phillipsmailto:notifications@github.com Sent: ‎1/‎31/‎2014 11:38 To: AstroProfundis/embrrmailto:embrr@noreply.github.com Cc: Shadowglen Elfmailto:shadowglen@outlook.com Subject: Re: [embrr] Ooops, an unknown error occured. Please go back or sign in again.是怎么回事？ (#50)

Also see same error. On Jan 31, 2014 11:36 AM, "Allen Zhong" notifications@github.com wrote:

话说最近观察到了若干次 http_code 为 0 或者 200 跳到错误页面的...

— Reply to this email directly or view it on GitHubhttps://github.com/AstroProfundis/embrr/issues/50#issuecomment-33759303 .

Reply to this email directly or view it on GitHub: https://github.com/AstroProfundis/embrr/issues/50#issuecomment-33759371

AstroProfundis commented 10 years ago

In my former exprience, this error usually come out when the server failed to connect to api.twitter.com or config.php misconfigured.

The errors with 0 and 200 code may due to twitter itself, as @shadowglen just said. I think we could wait for some more days and see if it got fixed, or if anyone can dump some useful data of what embrr got from api.twitter.com that then led it jump to the error page, it's appreaciated.

ghost commented 10 years ago

Is there a missing step in documentation for getting twitter auth key? On Jan 31, 2014 11:44 AM, "Allen Zhong" notifications@github.com wrote:

Reopened #50 https://github.com/AstroProfundis/embrr/issues/50.

— Reply to this email directly or view it on GitHubhttps://github.com/AstroProfundis/embrr/issues/50 .

AstroProfundis commented 10 years ago

Well, our doc don't really cover how to get a twitter oauth key, following dev.twitter.com is all I did to install embrr and is supposed to work for others. In fact, if the oauth key incorrect, you should not being able to login at all, then no way to see this error (or seeing it all the time).

ghost commented 10 years ago

So what everyone is using the same oauth key? That seems wrong. Seems like the first step in set up should be to get a key then proceed... On Jan 31, 2014 11:56 AM, "Allen Zhong" notifications@github.com wrote:

Well, our doc don't really cover how to get a twitter oauth key, following dev.twitter.com is all I did to install embrr and is supposed to work for others. In fact, if the oauth key incorrect, you should not being able to login at all, then no way to see this error (or seeing it all the time).

— Reply to this email directly or view it on GitHubhttps://github.com/AstroProfundis/embrr/issues/50#issuecomment-33760012 .

AstroProfundis commented 10 years ago

Yes using the same key is definitely wrong, we said in the README.md that "edit it with your own app information and upload it to your hosting directory." So you see, with own app info is the first step. We don't document about how to create a twitter app and get those info, though.

AstroProfundis commented 10 years ago

Forgot to explain, those keys in config.sample.php are from our upstream embr, witch is the app keys for a public site "embr". We believe the upstream author put it in template is to help those who don't know how to create new twitter apps, that they can use their own server but with the same "via" name.

We didn't considered this much, it's okay for me to change it to something like "REPLACE THIS WITH YOUR OWN APP KEY" if ppl think the current one inappropriate。

ghost commented 10 years ago

There must be some security and app limits that could be met all by going thru one persons app key.

I think better to put the documentation right in the config.sample.php

Good idea. On Jan 31, 2014 12:44 PM, "Allen Zhong" notifications@github.com wrote:

Forgot to explain, those keys in config.sample.php are from our upstream embr, witch is the app keys for a public site "embr". We believe the upstream author put it in template is to help those who don't know how to create new twitter apps, that they can use their own server but with the same "via" name.

We didn't considered this much, it's okay for me to change it to something like "REPLACE THIS WITH YOUR OWN APP KEY" if ppl think the current one inappropriate。

— Reply to this email directly or view it on GitHubhttps://github.com/AstroProfundis/embrr/issues/50#issuecomment-33761457 .

AstroProfundis commented 10 years ago

I've updated comments in config.sample.php in commit 580c5bff24101128e8c08028b6ab69fcd742a4c6

AstroProfundis commented 10 years ago

This issue disappeared in last few days, looks like a twitter side problem. I'll close this issue as "invalid" and "wontfix", if anyone proved it's on our side, just reopen this issue or open a new one.