# My extension sometimes doesn't work on Dev Rig

**URL:** <https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199>\
**Category:** Extensions\
**Created:** [December 24, 2018, 10:26am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199 "2018-12-24T10:26:06Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![dividivan](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dividivan/32/5514_2.png) [@dividivan](https://staging-discuss.dev.twitch.com/u/dividivan)\
**Post date:** [December 24, 2018, 10:26am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/1 "2018-12-24T10:26:06Z")

</div>

My dev rig sometimes stops works, It just shows an empty panel (it doesn’t reach the React code). I don’t see any error but I understand that the files are not being served properly.

I already had this problem and I fixed it but I am not sure how I did it and I have it again :S

I think that it’s happening when I go from hosted test to local test (but I am not sure).

Someone has experienced something like this?

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [December 24, 2018, 10:38am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/2 "2018-12-24T10:38:38Z")

</div>

> [@dividivan](#):
>
> I think that it’s happening when I go from hosted test to local test (but I am not sure).

If you change the extension configuration in the developer dashboard, you need to till the Rig to reload the manifest. Which on the browser based version is on the last tab iirc. And on the beta native rig on the Project Details.

Or a rig restart should fix it

---

<div class="post-metadata">

**Author:** ![dividivan](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dividivan/32/5514_2.png) [@dividivan](https://staging-discuss.dev.twitch.com/u/dividivan)\
**Post date:** [December 24, 2018, 11:16am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/3 "2018-12-24T11:16:34Z")

</div>

I have all updated and still not working

The extension is configured properly (It usually works with this)

 ![image](https://d2spem0quai2ol.cloudfront.net/original/2X/8/835b7f6496f99950628b305aab876f3eaff95b90.png)

I have restarted all; laptop, rig dev with yarn start and rig dev with the run file. I have even delete the old project and created a new one. Still I get a white panel.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [December 24, 2018, 8:40pm UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/4 "2018-12-24T20:40:31Z")

</div>

Then you need to check the chrome inspector for errors.

It sounds like you may have packaged your files incorrectly, and you are getting a 404

You need to package the files in your folder, not the folder itself

See

> [@\[SOLVED\] 404, The specified key does not exist](https://staging-discuss.dev.twitch.com/t/solved-404-the-specified-key-does-not-exist/11921):
>
> So I have been working on a panel extension for my stream and I got past the local testing, everything was working fine. I uploaded the files in a .zip to Twitch. I followed all the guides, made sure to include the extension helper JS file, but I am getting a 404 error when it tries to load the extension files form the Twitch CDN. I have tried created a new extension and uploaded the example project that Twitch has in the documentation to see if the issue would still happened and it did. I’m no…

In addition, make sure you are using relative URL’s to your assets/js/css

> [@\[SOLVED\] Getting 404 for hosted config.html asset](https://staging-discuss.dev.twitch.com/t/solved-getting-404-for-hosted-config-html-asset/18302/9):
>
> You need to use relative urls (not absolute) to load your css and js As your zip is uploaded to a sub folder of the extensions domain. (Something like extensionsdomain.twitch.tv/extensionversion/yourfiles)

---

<div class="post-metadata">

**Author:** ![dividivan](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dividivan/32/5514_2.png) [@dividivan](https://staging-discuss.dev.twitch.com/u/dividivan)\
**Post date:** [December 26, 2018, 9:21am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/5 "2018-12-26T09:21:35Z")

</div>

current status:

- Local test doesn’t work even creating a new version
- Hosted test works properly
- Chrome console shows this errors, but it was working with the same errors previously  
 ![image](https://d2spem0quai2ol.cloudfront.net/original/2X/3/339c1f5fcbe433287c5e3aa1f91fcccb841ef773.png)
- Rig terminal shows this one  
 ![image](https://d2spem0quai2ol.cloudfront.net/original/2X/f/fcdcd523923db82dc52adbaa42f9673cf2c5a9cf.png)

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [December 27, 2018, 12:24pm UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/6 "2018-12-27T12:24:06Z")

</div>

Chrome console messages are irrelevant here

Rig Terminal shows that server.js didn’t start.

As port 8000 is in use.

This might conflict with SLOBS if you are a SLOBS user, or Skype (though Skype is 80 and 8080 iirc usually)

---

<div class="post-metadata">

**Author:** ![dividivan](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dividivan/32/5514_2.png) [@dividivan](https://staging-discuss.dev.twitch.com/u/dividivan)\
**Post date:** [January 8, 2019, 9:28am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/7 "2019-01-08T09:28:10Z")

</div>

I have found a workaround for my problem.

I need to open directly the URL [https://localhost.rig.twitch.tv:8080/config.html](https://localhost.rig.twitch.tv:8080/config.html) in a browser and accept the “This connection is no private” warning. After that, the rig is working properly.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [January 8, 2019, 9:37am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/8 "2019-01-08T09:37:46Z")

</div>

That would be the self signed cert not being accepted or installed into your OS

And is not related to the screenshot/error you posted above…

---

<div class="post-metadata">

**Author:** ![dividivan](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dividivan/32/5514_2.png) [@dividivan](https://staging-discuss.dev.twitch.com/u/dividivan)\
**Post date:** [January 8, 2019, 9:42am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/9 "2019-01-08T09:42:28Z")

</div>

Yes, I know it. But I wasn’t receiving any error for the cert problem so I posted some errors that I had.  
It looks like I need to accept it twice each time I restart the rig dev.

---

<div class="post-metadata">

**Author:** ![cindy100295](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/cindy100295/32/6605_2.png) [@cindy100295](https://staging-discuss.dev.twitch.com/u/cindy100295)\
**Post date:** [June 26, 2019, 4:19am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/10 "2019-06-26T04:19:36Z")

</div>

Hey thanks for the solution. Thought the link [https://localhost.rig.twitch.tv:8080/panel.html](https://localhost.rig.twitch.tv:8080/panel.html) does not work for me. It says `This site can’t be reached localhost.rig.twitch.tv’s server IP address could not be found.`

I ran `yarn start` and the React component works fine on browser [https://localhost:8080/panel.html](https://localhost:8080/panel.html). Then I found on DevRig I should not click `Run Front End`, the it would show by itself. Not sure whether it is the correct way to run Boilerplate.

By the way I changed generate\_cert.sh according to this post: [https://github.com/twitchdev/extensions-boilerplate/issues/1](https://github.com/twitchdev/extensions-boilerplate/issues/1)

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [June 26, 2019, 10:33am UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/11 "2019-06-26T10:33:46Z")

</div>

> [@cindy100295](#):
>
> Hey thanks for the solution. Thought the link [https://localhost.rig.twitch.tv:8080/panel.html](https://localhost.rig.twitch.tv:8080/panel.html) does not work for me. It says `This site can’t be reached localhost.rig.twitch.tv’s server IP address could not be found.`

Did you add `localhost.rig.twitch.tv` to your hosts file? If you don’t want to do this you can use localhost instead just change your manifest

---

<div class="post-metadata">

**Author:** ![cindy100295](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/cindy100295/32/6605_2.png) [@cindy100295](https://staging-discuss.dev.twitch.com/u/cindy100295)\
**Post date:** [June 26, 2019, 5:31pm UTC](https://staging-discuss.dev.twitch.com/t/my-extension-sometimes-doesnt-work-on-dev-rig/19199/12 "2019-06-26T17:31:28Z")

</div>

Yeah I did. In `generate_cert.sh` it looks like this:

```auto
openssl req \
  -newkey rsa:4096 \
  -days 1001 \
  -nodes \
  -x509 \
  -subj "/C=US/ST=California/L=San Francisco/O=LULZCorp/OU=web/CN=localhost" \
  -extensions SAN \
  -config <( cat $( [["Darwin" = "$(uname -s)"]] && echo /System/Library/OpenSSL/openssl.cnf || echo /etc/ssl/openssl.cnf ) \
    <(printf "[SAN]\nsubjectAltName=DNS:localhost,DNS:localhost.rig.twitch.tv")) \
  -keyout "${DIR}/${NAME}.key" \
  -out "${DIR}/${NAME}.crt"

```
