# \[SOLVED\] Issue with Ratel or play.dgraph.io

**URL:** <https://discuss.dgraph.io/t/solved-issue-with-ratel-or-play-dgraph-io/17962>\
**Category:** Dgraph\
**Tags:** dgraph, ratel\
**Created:** [November 12, 2022, 1:13am UTC](https://discuss.dgraph.io/t/solved-issue-with-ratel-or-play-dgraph-io/17962 "2022-11-12T01:13:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [November 12, 2022, 1:13am UTC](https://discuss.dgraph.io/t/solved-issue-with-ratel-or-play-dgraph-io/17962/1 "2022-11-12T01:13:27Z")

</div>

Writing this recommendation here so that others in the future when searching the problem will understand how to solve it.

First, the problem is not Dgraph’s. But from Google. All Chromium-based browsers are limiting HTTPS service calls to other services without a TLS certificate. Google’s reasons are security based and beyond our control. It is not possible to do anything on our side.

The workaround is to use Firefox instead of any other Chromium-based browser. This is not just for Ratel, but for Tour tutorials as well.

e.g:

If you connect to `https://play.dgraph.io/?latest` and use a local server [http://localhost:8080](http://localhost:8080) - Chromium will block the connection. Then use Firefox instead.

If other problems like CORS exist. Keep using Firefox, but use an extension like “CORS Everywhere” or “Allow CORS: Access-Control-Allow-Origin”. But in general only changing the browser will solve.

Other solution is just run Ratel locally via Docker.

[https://hub.docker.com/r/dgraph/ratel/tags](https://hub.docker.com/r/dgraph/ratel/tags)

---

<div class="post-metadata">

**Author:** ![matthewmcneely](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/matthewmcneely/32/4774_2.png) [@matthewmcneely](https://discuss.dgraph.io/u/matthewmcneely)\
**Post date:** [November 14, 2022, 7:04pm UTC](https://discuss.dgraph.io/t/solved-issue-with-ratel-or-play-dgraph-io/17962/2 "2022-11-14T19:04:45Z")

</div>

There’s also a way in Chrome to allow access to non-SSL localhost: [Accessing http://localhost with chrome 100 - Google Chrome Community](https://support.google.com/chrome/thread/162605516/accessing-http-localhost-with-chrome-100?hl=en)

---

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [November 14, 2022, 7:53pm UTC](https://discuss.dgraph.io/t/solved-issue-with-ratel-or-play-dgraph-io/17962/3 "2022-11-14T19:53:46Z")

</div>

I’ve just tested this. But no lucky.

---

<div class="post-metadata">

**Author:** ![matthewmcneely](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/matthewmcneely/32/4774_2.png) [@matthewmcneely](https://discuss.dgraph.io/u/matthewmcneely)\
**Post date:** [November 14, 2022, 7:58pm UTC](https://discuss.dgraph.io/t/solved-issue-with-ratel-or-play-dgraph-io/17962/4 "2022-11-14T19:58:04Z")

</div>

> [@MichelDiz](#):
>
> But no lucky

Hmm, works for me ([https://play.dgraph.io](https://play.dgraph.io) connected my localhost:8080). My chrome version: 107.0.5304.87 (Official Build) (arm64)