search

diodechain / diode_client

Diode client written in GO that runs the Blockquick™ algorithm and a socks server to transmit data through diode ztna network.
https://diode.io/download
Other
66 stars 23 forks source link

Gateway with Custom Domain #99

Closed jimthedj65 closed 2 years ago

jimthedj65 commented 2 years ago

When I change the diode client to reference my domain name peerxc.link from ver 12.03 it worked fine. since 12.04 it was erratic and now since 12.07 it now no longer works.

`The changes are: the only changes are - fetch.go line 43 diode >>> peerxc

when I compile Diode Client version : v0.12.8-dirty 23 Mar 2022 INFO Checking for updates... INFO No updates INFO GO Version : go1.17.5 INFO Openssl Version : OpenSSL 1.1.1k 25 Mar 2021 INFO OS ARCH CPU : linux amd64 2(Didoe12.07) the gateway the new domain, I get errors below

Gateway side:03/23/2022 15:46:01 INFO Resolving BNS: peerxc server=eu2.prenet.diode.io:41046 03/23/2022 15:46:04 WARN Handshake error: **etl-test-stream.peerxc.link** device was not allowed key not found in merkle tree

etl-test-stream.peerxc.link is the client trying to connect to the gateway. On the browser side, I get a simple 404 and sometimes a diode branded 404 signifying that there may be connectivity issues.

peerxc.link is sat behind cloudflare.

any assistance on resolving the gateway issues to have my domain back online again, is appreciated, this will help us to move forward on the AVX acceleration.

jimthedj65 commented 2 years ago

After refreshing the master on github, we appear to have a new node/gateway error

04/01/2022 08:53:48 ERROR open ./priv/priv.pem: no such file or directory

not sure if its related.

jimthedj65 commented 2 years ago

On the browser side we can see that a certificate is not being generated anymore. we get:

This site can’t be reached etl-test-stream.peerxc.link refused to connect.
Try:

Checking the connection
[Checking the proxy and the firewall](chrome-error://chromewebdata/#buttons)
ERR_CONNECTION_REFUSED
jimthedj65 commented 2 years ago

this was resolved by running rm -rf ~/.local/share/certmagic and restarting the gateway.