2017-10-28 267 views
6

我正在使用Ruby on Rails構建一個Web應用程序。我使用Mailgun作爲這款應用程序的郵件。當我使用Facebook註冊時,它工作正常,但是當我嘗試使用電子郵件和密碼註冊時,我不斷收到此錯誤「554請激活您的Mailgun帳戶。檢查您的收件箱或登錄您的控制面板重新發送激活電子郵件。 「我已經授權給mailgun儀表板中的授權收件人。這裏是我的代碼:「554請激活您的Mailgun帳戶,檢查您的收件箱或登錄您的控制面板重新發送激活郵件。」錯誤Ruby on Rails

Registrations_controller.rb

class RegistrationsController < Devise::RegistrationsController 
    protected 
    def update_resource(resource,params) 
     resource.update_without_password(params) 
    end 
end 

配置/環境/ development.rb

Rails.application.configure do 
    # Settings specified here will take precedence over those in config/application.rb. 

    # In the development environment your application's code is reloaded on 
    # every request. This slows down response time but is perfect for development 
    # since you don't have to restart the web server when you make code changes. 
    config.cache_classes = false 

    # Do not eager load code on boot. 
    config.eager_load = false 

    # Show full error reports. 
    config.consider_all_requests_local = true 

    # Enable/disable caching. By default caching is disabled. 
    if Rails.root.join('tmp/caching-dev.txt').exist? 
    config.action_controller.perform_caching = true 

    config.cache_store = :memory_store 
    config.public_file_server.headers = { 
     'Cache-Control' => 'public, max-age=172800' 
    } 
    else 
    config.action_controller.perform_caching = false 

    config.cache_store = :null_store 
    end 

    # Don't care if the mailer can't send. 
    config.action_mailer.raise_delivery_errors = true 

    config.action_mailer.perform_caching = false 

    # Print deprecation notices to the Rails logger. 
    config.active_support.deprecation = :log 

    # Raise an error on page load if there are pending migrations. 
    config.active_record.migration_error = :page_load 

    # Debug mode disables concatenation and preprocessing of assets. 
    # This option may cause significant delays in view rendering with a large 
    # number of complex assets. 
    config.assets.debug = true 

    # Suppress logger output for asset requests. 
    config.assets.quiet = true 

    # Raises error for missing translations 
    # config.action_view.raise_on_missing_translations = true 

    # Use an evented file watcher to asynchronously detect changes in source code, 
    # routes, locales, etc. This feature depends on the listen gem. 
    config.file_watcher = ActiveSupport::EventedFileUpdateChecker 

    config.action_mailer.default_url_options = { host: 'localhost', port: 3000 } 

    config.action_mailer.delivery_method = :smtp 
    config.action_mailer.smtp_settings = { 
    address: 'smtp.mailgun.org', 
    port: 587, 
    domain: 'sandboxc77c3a9be90a494081dad1628d554337.mailgun.org', 
    authentication: 'plain', 
    user_name: '[email protected]', 
    password: 'password' 
} 


end 

initalizers/devise.rb

  # Use this hook to configure devise mailer, warden hooks and so forth. 
# Many of these configuration options can be set straight in your model. 
Devise.setup do |config| 
    # The secret key used by Devise. Devise uses this key to generate 
    # random tokens. Changing this key will render invalid all existing 
    # confirmation, reset password and unlock tokens in the database. 
    # Devise will use the `secret_key_base` as its `secret_key` 
    # by default. You can change it below and use your own secret key. 
    # config.secret_key = 'c6a5a4855ac1429f82d4a04dd9d2dda9d0bbae1a6252c3f7b7c954515169f2b693d53064f1b3656ad43ee8bcb8063d39fdc791d3885a2b6286a8280b2c4349b1' 

    # ==> Mailer Configuration 
    # Configure the e-mail address which will be shown in Devise::Mailer, 
    # note that it will be overwritten if you use your own mailer class 
    # with default "from" parameter. 
    config.mailer_sender = '[email protected]' 

    # Configure the class responsible to send e-mails. 
    # config.mailer = 'Devise::Mailer' 

    # Configure the parent class responsible to send e-mails. 
    # config.parent_mailer = 'ActionMailer::Base' 

    # ==> ORM configuration 
    # Load and configure the ORM. Supports :active_record (default) and 
    # :mongoid (bson_ext recommended) by default. Other ORMs may be 
    # available as additional gems. 
    require 'devise/orm/active_record' 

    # ==> Configuration for any authentication mechanism 
    # Configure which keys are used when authenticating a user. The default is 
    # just :email. You can configure it to use [:username, :subdomain], so for 
    # authenticating a user, both parameters are required. Remember that those 
    # parameters are used only when authenticating and not when retrieving from 
    # session. If you need permissions, you should implement that in a before filter. 
    # You can also supply a hash where the value is a boolean determining whether 
    # or not authentication should be aborted when the value is not present. 
    # config.authentication_keys = [:email] 

    # Configure parameters from the request object used for authentication. Each entry 
    # given should be a request method and it will automatically be passed to the 
    # find_for_authentication method and considered in your model lookup. For instance, 
    # if you set :request_keys to [:subdomain], :subdomain will be used on authentication. 
    # The same considerations mentioned for authentication_keys also apply to request_keys. 
    # config.request_keys = [] 

    # Configure which authentication keys should be case-insensitive. 
    # These keys will be downcased upon creating or modifying a user and when used 
    # to authenticate or find a user. Default is :email. 
    config.case_insensitive_keys = [:email] 

    # Configure which authentication keys should have whitespace stripped. 
    # These keys will have whitespace before and after removed upon creating or 
    # modifying a user and when used to authenticate or find a user. Default is :email. 
    config.strip_whitespace_keys = [:email] 

    # Tell if authentication through request.params is enabled. True by default. 
    # It can be set to an array that will enable params authentication only for the 
    # given strategies, for example, `config.params_authenticatable = [:database]` will 
    # enable it only for database (email + password) authentication. 
    # config.params_authenticatable = true 

    # Tell if authentication through HTTP Auth is enabled. False by default. 
    # It can be set to an array that will enable http authentication only for the 
    # given strategies, for example, `config.http_authenticatable = [:database]` will 
    # enable it only for database authentication. The supported strategies are: 
    # :database  = Support basic authentication with authentication key + password 
    # config.http_authenticatable = false 

    # If 401 status code should be returned for AJAX requests. True by default. 
    # config.http_authenticatable_on_xhr = true 

    # The realm used in Http Basic Authentication. 'Application' by default. 
    # config.http_authentication_realm = 'Application' 

    # It will change confirmation, password recovery and other workflows 
    # to behave the same regardless if the e-mail provided was right or wrong. 
    # Does not affect registerable. 
    # config.paranoid = true 

    # By default Devise will store the user in session. You can skip storage for 
    # particular strategies by setting this option. 
    # Notice that if you are skipping storage for all authentication paths, you 
    # may want to disable generating routes to Devise's sessions controller by 
    # passing skip: :sessions to `devise_for` in your config/routes.rb 
    config.skip_session_storage = [:http_auth] 

    # By default, Devise cleans up the CSRF token on authentication to 
    # avoid CSRF token fixation attacks. This means that, when using AJAX 
    # requests for sign in and sign up, you need to get a new CSRF token 
    # from the server. You can disable this option at your own risk. 
    # config.clean_up_csrf_token_on_authentication = true 

    # When false, Devise will not attempt to reload routes on eager load. 
    # This can reduce the time taken to boot the app but if your application 
    # requires the Devise mappings to be loaded during boot time the application 
    # won't boot properly. 
    # config.reload_routes = true 

    # ==> Configuration for :database_authenticatable 
    # For bcrypt, this is the cost for hashing the password and defaults to 11. If 
    # using other algorithms, it sets how many times you want the password to be hashed. 
    # 
    # Limiting the stretches to just one in testing will increase the performance of 
    # your test suite dramatically. However, it is STRONGLY RECOMMENDED to not use 
    # a value less than 10 in other environments. Note that, for bcrypt (the default 
    # algorithm), the cost increases exponentially with the number of stretches (e.g. 
    # a value of 20 is already extremely slow: approx. 60 seconds for 1 calculation). 
    config.stretches = Rails.env.test? ? 1 : 11 

    # Set up a pepper to generate the hashed password. 
    # config.pepper = '6bc2b1bff3932e8c90d4bdc72a796441ec839d1cafc371f15ed0585cbd0daf6108e84140221abbf970c8f1ddd38b3a0663abade7060d80490fa57131794ad9eb' 

    # Send a notification to the original email when the user's email is changed. 
    # config.send_email_changed_notification = false 

    # Send a notification email when the user's password is changed. 
    # config.send_password_change_notification = false 

    # ==> Configuration for :confirmable 
    # A period that the user is allowed to access the website even without 
    # confirming their account. For instance, if set to 2.days, the user will be 
    # able to access the website for two days without confirming their account, 
    # access will be blocked just in the third day. Default is 0.days, meaning 
    # the user cannot access the website without confirming their account. 
    # config.allow_unconfirmed_access_for = 2.days 

    # A period that the user is allowed to confirm their account before their 
    # token becomes invalid. For example, if set to 3.days, the user can confirm 
    # their account within 3 days after the mail was sent, but on the fourth day 
    # their account can't be confirmed with the token any more. 
    # Default is nil, meaning there is no restriction on how long a user can take 
    # before confirming their account. 
    # config.confirm_within = 3.days 

    # If true, requires any email changes to be confirmed (exactly the same way as 
    # initial account confirmation) to be applied. Requires additional unconfirmed_email 
    # db field (see migrations). Until confirmed, new email is stored in 
    # unconfirmed_email column, and copied to email column on successful confirmation. 
    config.reconfirmable = false 

    # Defines which key will be used when confirming an account 
    # config.confirmation_keys = [:email] 

    # ==> Configuration for :rememberable 
    # The time the user will be remembered without asking for credentials again. 
    # config.remember_for = 2.weeks 

    # Invalidates all the remember me tokens when the user signs out. 
    config.expire_all_remember_me_on_sign_out = true 

    # If true, extends the user's remember period when remembered via cookie. 
    # config.extend_remember_period = false 

    # Options to be passed to the created cookie. For instance, you can set 
    # secure: true in order to force SSL only cookies. 
    # config.rememberable_options = {} 

    # ==> Configuration for :validatable 
    # Range for password length. 
    config.password_length = 6..128 

    # Email regex used to validate email formats. It simply asserts that 
    # one (and only one) @ exists in the given string. This is mainly 
    # to give user feedback and not to assert the e-mail validity. 
    config.email_regexp = /\A[^@\s][email protected][^@\s]+\z/ 

    # ==> Configuration for :timeoutable 
    # The time you want to timeout the user session without activity. After this 
    # time the user will be asked for credentials again. Default is 30 minutes. 
    # config.timeout_in = 30.minutes 

    # ==> Configuration for :lockable 
    # Defines which strategy will be used to lock an account. 
    # :failed_attempts = Locks an account after a number of failed attempts to sign in. 
    # :none   = No lock strategy. You should handle locking by yourself. 
    # config.lock_strategy = :failed_attempts 

    # Defines which key will be used when locking and unlocking an account 
    # config.unlock_keys = [:email] 

    # Defines which strategy will be used to unlock an account. 
    # :email = Sends an unlock link to the user email 
    # :time = Re-enables login after a certain amount of time (see :unlock_in below) 
    # :both = Enables both strategies 
    # :none = No unlock strategy. You should handle unlocking by yourself. 
    # config.unlock_strategy = :both 

    # Number of authentication tries before locking an account if lock_strategy 
    # is failed attempts. 
    # config.maximum_attempts = 20 

    # Time interval to unlock the account if :time is enabled as unlock_strategy. 
    # config.unlock_in = 1.hour 

    # Warn on the last attempt before the account is locked. 
    # config.last_attempt_warning = true 

    # ==> Configuration for :recoverable 
    # 
    # Defines which key will be used when recovering the password for an account 
    # config.reset_password_keys = [:email] 

    # Time interval you can reset your password with a reset password key. 
    # Don't put a too small interval or your users won't have the time to 
    # change their passwords. 
    config.reset_password_within = 6.hours 

    # When set to false, does not sign a user in automatically after their password is 
    # reset. Defaults to true, so a user is signed in automatically after a reset. 
    # config.sign_in_after_reset_password = true 

    # ==> Configuration for :encryptable 
    # Allow you to use another hashing or encryption algorithm besides bcrypt (default). 
    # You can use :sha1, :sha512 or algorithms from others authentication tools as 
    # :clearance_sha1, :authlogic_sha512 (then you should set stretches above to 20 
    # for default behavior) and :restful_authentication_sha1 (then you should set 
    # stretches to 10, and copy REST_AUTH_SITE_KEY to pepper). 
    # 
    # Require the `devise-encryptable` gem when using anything other than bcrypt 
    # config.encryptor = :sha512 

    # ==> Scopes configuration 
    # Turn scoped views on. Before rendering "sessions/new", it will first check for 
    # "users/sessions/new". It's turned off by default because it's slower if you 
    # are using only default views. 
    # config.scoped_views = false 

    # Configure the default scope given to Warden. By default it's the first 
    # devise role declared in your routes (usually :user). 
    # config.default_scope = :user 

    # Set this configuration to false if you want /users/sign_out to sign out 
    # only the current scope. By default, Devise signs out all scopes. 
    # config.sign_out_all_scopes = true 

    # ==> Navigation configuration 
    # Lists the formats that should be treated as navigational. Formats like 
    # :html, should redirect to the sign in page when the user does not have 
    # access, but formats like :xml or :json, should return 401. 
    # 
    # If you have any extra navigational formats, like :iphone or :mobile, you 
    # should add them to the navigational formats lists. 
    # 
    # The "*/*" below is required to match Internet Explorer requests. 
    # config.navigational_formats = ['*/*', :html] 

    # The default HTTP method used to sign out a resource. Default is :delete. 
    config.sign_out_via = :delete 

    # ==> OmniAuth 
    # Add a new OmniAuth provider. Check the wiki for more information on setting 
    # up on your models and hooks. 
    # config.omniauth :github, 'APP_ID', 'APP_SECRET', scope: 'user,public_repo' 

    # ==> Warden configuration 
    # If you want to use other strategies, that are not supported by Devise, or 
    # change the failure app, you can configure them inside the config.warden block. 
    # 
    # config.warden do |manager| 
    # manager.intercept_401 = false 
    # manager.default_strategies(scope: :user).unshift :some_external_strategy 
    # end 

    # ==> Mountable engine configurations 
    # When using Devise inside an engine, let's call it `MyEngine`, and this engine 
    # is mountable, there are some extra configurations to be taken into account. 
    # The following options are available, assuming the engine is mounted as: 
    # 
    #  mount MyEngine, at: '/my_engine' 
    # 
    # The router that invoked `devise_for`, in the example above, would be: 
    # config.router_name = :my_engine 
    # 
    # When using OmniAuth, Devise cannot automatically set OmniAuth path, 
    # so you need to do it manually. For the users scope, it would be: 
    # config.omniauth_path_prefix = '/my_engine/users/auth' 

    config.omniauth :facebook , '1811726395785808' , '2fcf2b0c1a2232b2e0850f35706bebcd' , scope: 'email', info_fields:'email,name' 
end 

視圖/設計/註冊/ new.html.erb

<div class="row"> 
    <div class="col-md-4 col-md-offset-4"> 
<h2>Sign up</h2> 

<%= form_for(resource, as: resource_name, url: registration_path(resource_name)) do |f| %> 
    <%= render 'layouts/shared/devisemes' %> 

    <div class="form-group"> 
    <%= f.text_field :fullname, autofocus: true , placeholder: "Full Name" , class: "form-control" %> 
    </div> 

    <div class="form-group"> 
    <%= f.email_field :email, autofocus: true , placeholder: "Email" , class: "form-control" %> 
    </div> 

    <div class="form-group"> 
    <%= f.label :password %> 
    <% if @minimum_password_length %> 
    <em>(<%= @minimum_password_length %> characters minimum)</em> 
    <% end %><br /> 
    <%= f.password_field :password, autocomplete: "off" , placeholder: "Password" , class: "form-control" %> 
    </div> 



    <div class="actions"> 
    <%= f.submit "Sign up" , class: "btn btn-normal btn-block" %> 
    </div> 
<% end %> 

<%= link_to "Sign up with Facebook", user_facebook_omniauth_authorize_path , class: "btn btn-facebook btn-block"%> 


<%= render "devise/shared/links" %> 
</div> 
</div> 

授權的接收者截圖

enter image description here

圖中所示爲終端

消息時,我檢查終端中的日誌我得到這個消息whi ch會正確發送電子郵件,但是,即使電子郵件語法出現在終端中,它也不會顯示在我的電子郵件收件箱中。這是數形式的終端

Rendering devise/mailer/confirmation_instructions.html.erb 
    Rendered devise/mailer/confirmation_instructions.html.erb (0.8ms) 
Devise::Mailer#confirmation_instructions: processed outbound mail in 17.6ms 
Sent mail to [email protected] (6432.1ms) 
Date: Mon, 06 Nov 2017 10:56:18 +0300 
From: [email protected] 
Reply-To: [email protected] 
To: [email protected] 
Message-ID: <[email protected]> 
Subject: Confirmation instructions 
Mime-Version: 1.0 
Content-Type: text/html; 
charset=UTF-8 
Content-Transfer-Encoding: 7bit 

<p>Welcome [email protected]!</p> 

<p>You can confirm your account email through the link below:</p> 

<p><a href="http://localhost:3000/confirmation?confirmation_token=_vmddjdeidjfjkdl">Confirm my account</a></p> 

Completed 500 Internal Server Error in 6454ms (ActiveRecord: 0.3ms) 



Net::SMTPFatalError (554 Please activate your Mailgun account. Check your inbox or log in to your control panel to resend the activation email. 
): 
+1

發現好像給我你需要登錄你的Mailgun帳戶並激活它,它的確是在你的問題的標題中:「554請激活你的Mailgun帳戶,檢查你的收件箱或登錄到你的控制面板重新發送激活郵件」error Ruby on Rails –

+0

我做了但我仍然得到這個錯誤 – AHmed

+0

你有沒有考慮聯繫在Mailgun的支持? – spickermann

回答

4

原因:按照您的SMTP配置,您使用的Mailgun沙箱發送域,但你設置發件人是[email protected],這不屬於沙箱發送域。解決方案:

出於測試目的,使用沙箱發送域

保持。它需要2件東西

  1. 由於發送域爲sandboxc77c3a9be90a494081dad1628d554337.mailgun.org,發件人必須來自此域。因此,更改Devise配置將發件人設置爲[email protected]而不是[email protected]
  2. 作爲你的描述,你可能已經做了這一步。 Mailgun沙箱發送域只允許發送電子郵件給授權收件人。因此,請訪問沙箱域設置(根據您的SMTP信息,您應該能夠訪問https://app.mailgun.com/app/domains/sandboxc77c3a9be90a494081dad1628d554337.mailgun.org)並添加您的電子郵件地址(用於在您的應用程序上註冊帳戶的電子郵件地址,該地址將收到Devise確認電子郵件)。詳細步驟添加授權的接收者可以在Mailgun help page

正如我上面提到的,你正在使用沙箱發送域,這是不能被公開用於真正的用戶可以找到另外的生產用。您需要添加igloo.com(您想使用發件人假設是[email protected])作爲發送域(指南可在Mailgun help page上Mailgun被發現和驗證(指南可在Mailgun help page

+0

我確實在Devlopment模式下添加了代碼,並且需要執行兩個步驟,但仍然出現同樣的錯誤,我甚至授權Mailgun上的電子郵件和重置數據庫,但仍然是錯誤不會消失。 – AHmed

+0

您正在關注**用於測試目的**,對嗎?你可以在'initalizers/devise.rb'中分享你的新'mailer_sender'和Mailgun上'Authorizied Recepients'的截圖嗎? –

+0

我使用所需文件編輯了代碼 – AHmed