2014-07-14 58 views
0

我有一個Rails應用程序使用設計與可確認的電子郵件。電子郵件發送正常,確認鏈接正在開發中完美運行。但在Heroku的製作中,它根本不起作用。Rails w /設計,確認令牌不生產

此外,電子郵件在生產時發送的罰款,令牌生成,但單擊時,頁面只是重定向到'重新發送確認說明'頁面。生產中是否缺少一些東西來完成這項工作?任何建議或幫助?

這裏是我的日誌從發展:

Started GET "https://stackoverflow.com/users/confirmation?confirmation_token=SusKNC1PyZ4ayJxL9asR" for 127.0.0.1 at 2014-07-13 21:32:02 -0400 
Processing by Devise::ConfirmationsController#show as HTML 
    Parameters: {"confirmation_token"=>"SusKNC1PyZ4ayJxL9asR"} 
    User Load (0.9ms) SELECT "users".* FROM "users" WHERE "users"."confirmation_token" = '28535b0ce6b4cb809463749ccad8ae0c8e92f6e7ce6ea2b9262dc6be87eb1fff' ORDER BY "users"."id" ASC LIMIT 1 
    (0.1ms) BEGIN 
    SQL (0.9ms) UPDATE "users" SET "confirmation_token" = $1, "confirmed_at" = $2, "updated_at" = $3 WHERE "users"."id" = 3 [["confirmation_token", nil], ["confirmed_at", "2014-07-14 01:32:02.960080"], ["updated_at", "2014-07-14 01:32:02.960674"]] 
    (0.5ms) COMMIT 
Redirected to http://localhost:3000/users/sign_in 

,這裏是從Heroku的

2014-07-14T01:36:05.606623+00:00 heroku[router]: at=info method=GET path="https://stackoverflow.com/users/confirmation" host=www.———.— request_id=76de591e-0948-4b89-93b1-eeb9431b2b9c fwd="72.229.255.68" dyno=web.1 connect=2 service=18 status=304 bytes=1218 
2014-07-14T01:36:05.585691+00:00 app[web.1]: Started GET "https://stackoverflow.com/users/confirmation" for 72.229.255.68 at 2014-07-14 01:36:05 +0000 
2014-07-14T01:36:05.594512+00:00 app[web.1]: Rendered devise/shared/_links.html.haml (0.5ms) 
2014-07-14T01:36:05.594570+00:00 app[web.1]: Rendered devise/confirmations/new.html.haml within layouts/application (3.1ms) 
2014-07-14T01:36:05.596841+00:00 app[web.1]: Rendered layouts/_header.html.haml (1.1ms) 
2014-07-14T01:36:05.588617+00:00 app[web.1]: Processing by Devise::ConfirmationsController#show as HTML 
2014-07-14T01:36:05.597479+00:00 app[web.1]: Completed 200 OK in 9ms (Views: 6.3ms | ActiveRecord: 0.0ms) 

回答

0

我很愚蠢,我的日誌只是解決了這個問題我提交後。問題出在我的網址上。我在我的production.rb文件中爲smtp設置進入了根域。但我實際上有一個www域,即根域重定向。 Ugh

+0

嗨斯科特,請你可以擴展一下你的解決方案 – ARTLoe

1

我有同樣的錯誤:生產中的「確認不能爲空」,即使它在我的本地機器上工作。對我來說,問題是WWWhisper的免費帳戶不允許未經授權的訪問,並將電子郵件確認鏈接視爲未經授權。

+0

這是對我來說是什麼。 – sabaeus