soyking / e3w Goto Github PK

Hi,
When I enabled auth on etcd and run e3w with auth:true I have an issue like

When I try to add delete edit user or role in Auth section there is an error like etcdclient: no available endpoints. I can put and get key values I also can see members status however, I couldn't do anything on auth . Can you check this issue ?

How to change base path?

i want to run the e3w behind reverse proxy and /e3w path.

Thank you.

Hello,

I started to use your project and I could install, see the etcd member on my server, create keys on it UI, but if i go to my etcd it is not there.

So i just don't understand how its possible ? Am I misunderstanding something ?

I even thought I wasn't using my etcd, but when I shut it down I can't see any data on the UI.

I see it uses my etcd, but why cant i find its data on the etcd ?

Best Regards.

i found #1, but it's old. thank your very much.

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle @~prebuild: @
6 silly lifecycle @~prebuild: no script for prebuild, continuing
7 info lifecycle @~build: @
8 verbose lifecycle @~build: unsafe-perm in lifecycle true
9 verbose lifecycle @~build: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;D:\Go\GOPATH\src\github.com\soyking\e3w\static\node_modules.bin;C:\Users\Administrator\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\local\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\bin;C:\Users\Administrator\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;D:\Program Files\TortoiseSVN\bin;D:\Program Files\Git\cmd;C:\ProgramData\ComposerSetup\bin;D:\Program Files\Bitvise SSH Client;D:\webserver\mysql\bin;D:\Go\GOPATH\bin;D:\Program Files\protoc-3.4.0-win32\bin;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files\Microsoft SQL Server\100\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\Python27;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft SQL Server\100\DTS\Binn;D:\Go\bin;C:\Program Files (x86)\Yarn\bin;%NVM_HOME%;%NVM_SYMLINK%;C:\Program Files\nodejs;D:\webserver\php-7.1.8;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;D:\Program Files\win_flex_bison;D:\Program Files\apache-maven-3.5.2\bin;C:\Program Files\Microsoft VS Code\bin;C:\Users\Administrator\AppData\Local\Android\Sdk\tools;C:\Users\Administrator\AppData\Local\Android\Sdk\platform-tools;E:\tools\ossutil64;C:\Users\Administrator\AppData\Local\Yarn\bin;C:\Users\Administrator\AppData\Local\Programs\Fiddler;C:\Users\Administrator\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\Administrator\AppData\Roaming\npm;D:\Program Files\Git\usr\bin\vendor_perl;D:\Program Files\Git\usr\bin\core_perl
10 verbose lifecycle @~build: CWD: D:\Go\GOPATH\src\github.com\soyking\e3w\static
11 silly lifecycle @~build: Args: [ '/d /s /c', './node_modules/webpack/bin/webpack.js' ]
12 silly lifecycle @~build: Returned: code: 1 signal: null
13 info lifecycle @~build: Failed to exec build script
14 verbose stack Error: @ build: ./node_modules/webpack/bin/webpack.js
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:194:7)
14 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:194:7)
14 verbose stack at maybeClose (internal/child_process.js:899:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid @
16 verbose cwd D:\Go\GOPATH\src\github.com\soyking\e3w\static
17 error Windows_NT 10.0.16299
18 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "build"
19 error node v7.7.4
20 error npm v4.1.2
21 error code ELIFECYCLE
22 error @ build: ./node_modules/webpack/bin/webpack.js
22 error Exit status 1
23 error Failed at the @ build script './node_modules/webpack/bin/webpack.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error ./node_modules/webpack/bin/webpack.js
23 error You can get information on how to open an issue for this project with:
23 error npm bugs
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

e3w is ignoring TLS options and serving on HTTP port even though I specify TLS options like following.

cert_file=/app/tls/cert.pem
key_file=/app/tls/key.key
ca_file=/app/tls/ca.pem

I tried to change default config and overwrite it using environment variables but did not work either case.

I think following line is the source of this problem.

Even though TLS options are specified Run function is called instead of RunTLS function of gin.

func (engine *Engine) RunTLS(addr, certFile, keyFile string) (err error) {...}

Maybe you can add a simple check like this.

if tls.config exists
    router.RunTLS(...)
else
    router.Run(...)

Maybe you can save it to disk, or a special key e.g.: /e3w/dirs/blahblah

When I use -d to run e3w instead of -it , docker logs show nothing.

now , I push the image to server and every one can modify the value of any key.
I hope some security policy to it~

And a other question is, the "setting" page has no submit button, is it right?

thank u

After the e3w service runs for a period of time, the error is as follows:

e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.534Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":83,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.666Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":84,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.777Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":85,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:51.928Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":86,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.031Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":87,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.176Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":88,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.275Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":89,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.403Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":90,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.513Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":91,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.648Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":92,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.750Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":93,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.888Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":94,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:52.988Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":95,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.122Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":96,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.243Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":97,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.381Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":98,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}
e3w-e3w-1  | {"level":"warn","ts":"2023-05-05T06:37:53.505Z","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00046f6c0/10.0.2.15:42379","attempt":99,"error":"rpc error: code = Unauthenticated desc = etcdserver: invalid auth token"}

After restarting the service, it will be fine, how to solve this problem without restarting the service

Thanks!!!

When I put key value with etcdctl I couldn't see them on this web ui. Likewise, I couldn't get with etcdctl kvs which I put via this web ui.

I just added e3w to my Kubernetes deploy, and was a little confused that I couldn't see any keys in etcd. Then I tried adding a couple of keys:

And looked for them in etcd:

# ETCDCTL_API=3 etcdctl --endpoints=localhost:2379 get --prefix ""
e3w_test/abcd
test
e3w_test/test
{test:2, foo: "bar"}

Looks like everything is prefixed with "e3w_test" by default, which seems like a weird default.

Is there any way I can clear this default without generating a new config file? An environment variable or something? I'd rather not create a config map just for this. :P

Or maybe the default should be no prefix when you bring up a clean docker image?

It would be nice if you add a license file - preferably MIT.

error shows: failed to create new OS thread (have 2 already; errno=22)
more info if there is still someone interest

Hello,

Is there a way to use API V2 and still see its data on etcd and UI as I would do that on V3?

I believe I can organize it better once I could create some directories for specific settings.

For example :

/project/database/mongo/host 192.168.30.40

/project/site/url github.com

I have like 500 configs that I would set on etcd, but it wouldn't be nice to see/change them on the same page/view

THank you.

you can see it form https://hub.docker.com/r/cnjackhack/e3w/
dockerFile:

FROM buildpack-deps:jessie-scm 
MAINTAINER jack [email protected]
WORKDIR /app
EXPOSE 8080
COPY ./app /app
RUN chmod +x /app/e3w
CMD ["/app/e3w"]

I have created a user and I want to login with those login credentials. How can I do this? It always logins with root user and doesn't ask for password. And in the settings tab, setting up a username and password is available but no save button.

How can I do this? and logs in as another user with limited access?

Hi MAte

It would be useful if we could have the binary on the releases tab.
Thx for your effort on the project. Top notch.

BR

Jo

Does e3w support arm architecture

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'publish' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prepublish', 'publish', 'postpublish' ]
5 info lifecycle @~prepublish: @
6 silly lifecycle @~prepublish: no script for prepublish, continuing
7 info lifecycle @~publish: @
8 verbose lifecycle @~publish: unsafe-perm in lifecycle true
9 verbose lifecycle @~publish: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/usr/dong/e3w/static/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
10 verbose lifecycle @~publish: CWD: /usr/dong/e3w/static
11 silly lifecycle @~publish: Args: [ '-c',
11 silly lifecycle 'NODE_ENV=production npm run build -- --optimize-minimize' ]
12 silly lifecycle @~publish: Returned: code: 1 signal: null
13 info lifecycle @~publish: Failed to exec publish script
14 verbose stack Error: @ publish: NODE_ENV=production npm run build -- --optimize-minimize
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:886:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid @
16 verbose cwd /usr/dong/e3w/static
17 error Linux 3.10.0-514.10.2.el7.x86_64
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "publish"
19 error node v6.10.1
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error @ publish: NODE_ENV=production npm run build -- --optimize-minimize
22 error Exit status 1
23 error Failed at the @ publish script 'NODE_ENV=production npm run build -- --optimize-minimize'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error NODE_ENV=production npm run build -- --optimize-minimize
23 error You can get information on how to open an issue for this project with:
23 error npm bugs
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Wanted to give role a view permission on everything but couldn't figure out if thats possible. I tried prefix with / but permission denied. I had to use etcdctl role grant-permission browser --prefix=true read e3w_test

Is that say can not manager the real etcd root key "/"?