cannot login to registry.gitlab.com
docker login [registry.gitlab.com](http://registry.gitlab.com) -u [myemail@example.com](mailto:myemail@example.com) -p mypassword

keep getting "error response from daemon: get <https://registry.gitlab.com/v2/:> error parsing http 403 response body: unexpected end of json input: "

anyone has the similar issue?
hello [@cjiang1](/u/cjiang1),

welcome to gitlab forum - thanks for your first contribution :slightly\_smiling\_face:

i think this is most probably caused by a misconfiguration - here’s an [example](https://gitlab.com/gitlab-org/gitlab-ce/issues/48349#note_129188834), fyi.
fwiw, i’m now using the “official” [docker login](https://github.com/marketplace/actions/docker-login) action with a docker hub [access token](https://docs.docker.com/docker-hub/access-tokens):

- name: docker login

uses: docker/login-action@v1

with:

username: ${{ secrets.docker\_username }}

password: ${{ secrets.docker\_token }}

:rocket: hi [@dr\_rainer\_demski](/u/dr_rainer_demski), welcome to the asana community forum :wave:t2:

in this case, i would suggest reaching out to our support team with the unique error code received as mentioned in the pop-up :slight\_smile:

you can reach out to the support team by clicking the support form prompt in the pop-up … try checking if your mail server can actually be reached from your discourse server. easiest way to do that would be to run ./discourse-doctor

nb: what happens if you remove the smtp authentication string from the configuration and rebuild? hey [@j.kassner](/u/j.kassner),

please see the solution to your question here:

[image]

["signuture is invalid" cdn 1.7.10 js viewer](https://devforum.zoom.us/t/signuture-is-invalid-cdn-1-7-10-js-viewer/24302/4) [web sdk](/c/web-sdk/13)

hey [@j.amelsberg](/u/j.amelsberg),

it appears you are using your sdk app key and secret to generate the signature. you need to use your jwt key and secret app to ge… You can post a hijackthis log and i can take a look at it for you. Malware might be the cause. after further research and coming across [this answer to a similar issue](https://community.auth0.com/t/failed-silent-auth-login-required/33165/39), i made the switch to auth0’s custom domain solution and it fixed all of the issues mentioned above. this topic can be closed! interesting.... hmm, it looks that the ./bin/elasticsearch script is requiring the keystore password input from stdin

if you look at the actual script that starts ./bin/elasticsearch you can see why.

from the script

# get keystore password before setting java options to avoid

# conflicting gc con… was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . since the error is on websockets, it is almost certainly a proxy layer somewhere that doesn’t support websockets, which is different on the two clusters (i.e. between you and any jupyterhub’s proxy-public entrypoint, rather than any part of jupyterhub itself or any of jupyterhub’s own configuration)… this is because you have a space between fields. 

program files (x86), avast software, it will continue to get this error because of the separation. try enclosing it into quotations. such as:get-content "c:\program files (x86)\avast software\business agent\log.txt"orget-content "c:\program files (x86)\avast software\business agent"\log.txt