# Discourse Development: Failed to register/update a ServiceWorker

**URL:** <https://meta.discourse.org/t/discourse-development-failed-to-register-update-a-serviceworker/89055>\
**Category:** Product Support\
**Created:** [June 3, 2018, 6:29pm UTC](https://meta.discourse.org/t/discourse-development-failed-to-register-update-a-serviceworker/89055 "2018-06-03T18:29:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kleinfreund](https://avatars.discourse-cdn.com/v4/letter/k/a6a055/32.png) [@kleinfreund](https://meta.discourse.org/u/kleinfreund)\
**Post date:** [June 5, 2018, 2:23pm UTC](https://meta.discourse.org/t/discourse-development-failed-to-register-update-a-serviceworker/89055/3 "2018-06-05T14:23:12Z")

</div>

Going to the settings shows “force https” as being disabled. I haven’t changed any discourse setting or configuration after cloning the repository and running it. I’ve just worked on a plugin. No other files were changed.

Running the command `bin/rails c` doesn’t provide any hint that seems to be relevant, either. Maybe it’s something else?

```plaintext
phil@RAUMSTATION in ~/dev/repos/discourse on master
👻 bin/rails c             
/home/phil/.rvm/gems/ruby-2.4.1/gems/i18n-0.8.6/lib/i18n.rb:12: warning: already initialized constant I18n::RESERVED_KEYS
/home/phil/.rvm/gems/ruby-2.4.1/gems/i18n-0.8.6/lib/i18n.rb:12: warning: previous definition of RESERVED_KEYS was here
/home/phil/.rvm/gems/ruby-2.4.1/gems/i18n-0.8.6/lib/i18n.rb:13: warning: already initialized constant I18n::RESERVED_KEYS_PATTERN
/home/phil/.rvm/gems/ruby-2.4.1/gems/i18n-0.8.6/lib/i18n.rb:13: warning: previous definition of RESERVED_KEYS_PATTERN was here
Loading development environment (Rails 5.1.4)
[1] pry(main)> 

```

---

_[View the full topic](https://meta.discourse.org/t/discourse-development-failed-to-register-update-a-serviceworker/89055)._