Closed ghost closed 5 years ago
In the latest Dgraph release v1.0.16, ACLs are not available. And for the upcoming v1.1 they'll be available as an enterprise feature and are not enabled by default. Can you share your cluster set up? In the Getting Started page I don't see any instructions that would turn on ACLs.
So, are you saying that there is no login / password required for Ratel to connect?
When I start Ratel, a default username groot
is visible in the login form. When I delete it the Login
button gets disabled.
I tried using the docker-compose.yml
file in the Getting Started originally, but when that didn't work I manually setup each container using Portainer. Perhaps I did something wrong there, but I can figure that out...I'm just not sure about the ratel login/password thing.
I guess one other thing that I don't understand is: Why does the server
entry in your docker-compose.yml
specify port 7080
here in command: dgraph alpha --my=server:7080 --lur_mb=2048 --zero:5080
but it exposes ports 8080
and 9080
for that same server
?
version: "3.2"
services:
zero:
image: dgraph/dgraph:latest
volumes:
- type: volume
source: dgraph
target: /dgraph
volume:
nocopy: true
ports:
- 5080:5080
- 6080:6080
restart: on-failure
command: dgraph zero --my=zero:5080
server:
image: dgraph/dgraph:latest
volumes:
- type: volume
source: dgraph
target: /dgraph
volume:
nocopy: true
ports:
- 8080:8080
- 9080:9080
restart: on-failure
command: dgraph alpha --my=server:7080 --lru_mb=2048 --zero=zero:5080
ratel:
image: dgraph/dgraph:latest
volumes:
- type: volume
source: dgraph
target: /dgraph
volume:
nocopy: true
ports:
- 8000:8000
command: dgraph-ratel
volumes:
dgraph:
I got it working by exposing port 7080
. After that, zero
didn't have any connection errors in the logs.
Anyway, while this was all possibly more difficult than it needed to be - I'll just close this issue and keep exploring. Thanks!
the same problem. After installation. Ratel webpage can be access but can not connect to dgraph server.
Change the default server URL port form 8000
to 8080
. Then it will work.
The default 8000 is the port for Ratel. 8080 for dgraph database itself.
I setup dgraph to run locally. Run zero using: dgraph zero --my=localhost:5080 and alpha using: dgraph alpha --lru_mb=1024 --my=localhost:7080 --zero=localhost:5080
Open Ratel UI in browser: localhost:8000 there trying to connect alpha using: localhost:8080 not connecting. ACL user and password field is available with groot as default. How to remove the username and password field.
Why is this closed? The original question was never answered.
And no explanation ... beyond
The "server URL" is confusing. There are multiple ports in use by the setup e.g. 5080,6080,8000,8080,9080 - there is no indication what the proper port would be. Entering the port 8080 in my case helped but i don't know why and which port this is. Why does the software not simply try out a few default ports and checks whether the wanted server is behind the port or at least have a button for auto-detection? The ACL username/password should simply vanish and it could also be determined by asking the server what the state of affairs is e.g. ACL is enabled. IMHO the current UI is horrible.
Using the latest and dev versions I see no changes that address this. Why ot spend some time on the UI and mature it a bit. Address the removal of connections, address the ACL and defaulted groot login entry. One cannot say that is reserved for our enterprise version and yet not provide some semblence of functionality. Many companies offer the most mundane enterprise features. Even Neo4J provides a full enterprise version to developers with some restrictions (contractual).
Some advice here, new products/companies come and go quickly, you want to gain traction then address the issues in this thread. If you need help doing so reach out to me directly. The UI to dgraph is the key interface for most trying this out or trying to evaluate it over ArangoDb, Neo4j, OrientDB (not procured by SAP), so many on the market now and yet only a few have great UI.
Please address these outlined issues above, perhaps puttng a checkbox next to ACL to enable/disable. I have also noticed that the entry field for dgraph-zero is being truncated by a single digit. Also, there seems to be no way to remove prior connections, they just keep piling up. First and foremost there are many UI designs available as reference designs, no need to omit key elements even upon a first release. It's like taking a cake out of the oven before it's fully cooked, it might taste great, texture sucks, people wont eat it.
DB
Hey guys, sorry for the delay. The default password for groot is password
.
The server URL to use in Ratel UI is the Dgraph's API endpoint. Which is in general at localhost:8080
see https://dgraph.io/docs/deploy/ports-usage/#ports-used-by-different-nodes
The ACL username/password should simply vanish and it could also be determined by asking the server what the state of affairs is e.g. ACL is enabled. IMHO the current UI is horrible. from @WolfgangFahl
Yeah, I know that is confusing sometimes. I have created this issue here https://github.com/dgraph-io/dgraph/issues/5234 to address this. Now that it is implemented we can do something about it. My idea was that Ratel would make it "disabled" visually.
But, you don't need to use ACL or login to it. You can use the "connect" button and after you see 3 greens you can close the box.
PS. BTW, all issues on Github aren't being monitored. You should start topics/questions/issues at https://discuss.dgraph.io/
Thanks for the suggestion @MichelDiz and @DarkBlaez.
Hey guys, sorry for the delay. The default password for groot is
password
. The server URL to use in Ratel UI is the Dgraph's API endpoint. Which is in general atlocalhost:8080
see https://dgraph.io/docs/deploy/ports-usage/#ports-used-by-different-nodesThe ACL username/password should simply vanish and it could also be determined by asking the server what the state of affairs is e.g. ACL is enabled. IMHO the current UI is horrible. from @WolfgangFahl
Yeah, I know that is confusing sometimes. I have created this issue here #5234 to address this. Now that it is implemented we can do something about it. My idea was that Ratel would make it "disabled" visually.
But, you don't need to use ACL or login to it. You can use the "connect" button and after you see 3 greens you can close the box.
PS. BTW, all issues on Github aren't being monitored. You should start topics/questions/issues at https://discuss.dgraph.io/
The default password is not 'password'.
@wwwjljj could you double check the server URL? Particularly the port. Usually, the port is 8080, not 8000.
@wwwjljj could you double check the server URL? Particularly the port. Usually, the port is 8080, not 8000. Still not work.
What is the new error message you got? Please remember to click 'Connect' after entering the host
On Wed, Aug 19, 2020 at 18:11:57, 王金磊 < notifications@github.com > wrote:
@ wwwjljj ( https://github.com/wwwjljj ) could you double check the server URL? Particularly the port. Usually, the port is 8080, not 8000. Still not work. image ( https://user-images.githubusercontent.com/1861277/90635787-3c043a00-e25c-11ea-9a47-e2e3e6597421.png ) image ( https://user-images.githubusercontent.com/1861277/90635823-4c1c1980-e25c-11ea-9d44-2ff9c23652d6.png )
— You are receiving this because you commented. Reply to this email directly, view it on GitHub ( https://github.com/dgraph-io/dgraph/issues/3680#issuecomment-676288674 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAIPOVBFOCPZIFIOQVDWUTSBPCBLANCNFSM4IEUQP2A ).
What is the new error message you got? Please remember to click 'Connect' after entering the host … On Wed, Aug 19, 2020 at 18:11:57, 王金磊 < @.*** > wrote: > > > @ wwwjljj ( https://github.com/wwwjljj ) could you double check the server > URL? Particularly the port. Usually, the port is 8080, not 8000. > Still not work. > image ( > https://user-images.githubusercontent.com/1861277/90635787-3c043a00-e25c-11ea-9a47-e2e3e6597421.png > ) > image ( > https://user-images.githubusercontent.com/1861277/90635823-4c1c1980-e25c-11ea-9d44-2ff9c23652d6.png > ) > > — You are receiving this because you commented. Reply to this email directly, view it on GitHub ( #3680 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAIPOVBFOCPZIFIOQVDWUTSBPCBLANCNFSM4IEUQP2A ).
There is no need to click the login button here. You should just be able to click Continue. In this picture, it looks like you have already been connected (and there are three green circles which indicate this).
On Wed, Aug 19, 2020 at 18:16:37, 王金磊 < notifications@github.com > wrote:
What is the new error message you got? Please remember to click 'Connect' after entering the host … ( # ) On Wed, Aug 19, 2020 at 18:11:57, 王金磊 < @.*** > wrote: > > > @ wwwjljj ( https:/ / github. com/ wwwjljj ( https://github.com/wwwjljj ) ) could you double check the server > URL? Particularly the port. Usually, the port is 8080, not 8000. > Still not work. > image ( > https:/ / user-images. githubusercontent. com/ 1861277/ 90635787-3c043a00-e25c-11ea-9a47-e2e3e6597421. png ( https://user-images.githubusercontent.com/1861277/90635787-3c043a00-e25c-11ea-9a47-e2e3e6597421.png ) > ) > image ( > https:/ / user-images. githubusercontent. com/ 1861277/ 90635823-4c1c1980-e25c-11ea-9d44-2ff9c23652d6. png ( https://user-images.githubusercontent.com/1861277/90635823-4c1c1980-e25c-11ea-9d44-2ff9c23652d6.png ) > ) > > — You are receiving this because you commented. Reply to this email directly, view it on GitHub ( #3680 (comment) ( https://github.com/dgraph-io/dgraph/issues/3680#issuecomment-676288674 ) ) , or unsubscribe ( https:/ / github. com/ notifications/ unsubscribe-auth/ AAAIPOVBFOCPZIFIOQVDWUTSBPCBLANCNFSM4IEUQP2A ( https://github.com/notifications/unsubscribe-auth/AAAIPOVBFOCPZIFIOQVDWUTSBPCBLANCNFSM4IEUQP2A ) ).
image ( https://user-images.githubusercontent.com/1861277/90636334-0744b280-e25d-11ea-9954-eef6002cfa8c.png )
— You are receiving this because you commented. Reply to this email directly, view it on GitHub ( https://github.com/dgraph-io/dgraph/issues/3680#issuecomment-676295214 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAIPOUZA6MC4P5AO54ZLELSBPCS3ANCNFSM4IEUQP2A ).
I think I have seen this issue before. He is using 20.03.0. @wwwjljj can you start from scratch or upgrade to the latest Dgraph version? Or pass the console log error on your browser. That might help to know what is happening.
I think I have seen this issue before. He is using 20.03.0. @wwwjljj can you start from scratch or upgrade to the latest Dgraph version? Or pass the console log error on your browser. That might help to know what is happening. Maybe that is my question: I run the command below in the docs:
docker run --rm -d -it -p 8080:8080 -p 9080:9080 -p 8000:8000 -v ~/dgraph:/dgraph dgraph/standalone:v20.03.0
it seems the version is v20.03.
Now I run the command:
docker run --rm -d -it -p 8080:8080 -p 9080:9080 -p 8000:8000 -v ~/dgraph:/dgraph dgraph/standalone:latest
I will try nginx next.
There is no need to click the login button here. You should just be able to click Continue. In this picture, it looks like you have already been connected (and there are three green circles which indicate this). … On Wed, Aug 19, 2020 at 18:16:37, 王金磊 < @. > wrote: > > > What is the new error message you got? Please remember to click 'Connect' > after entering the host > … ( # ) > On Wed, Aug 19, 2020 at 18:11:57, 王金磊 < @. > wrote: > > > @ wwwjljj ( > https:/ / github. com/ wwwjljj ( https://github.com/wwwjljj ) ) could you > double check the server > URL? Particularly the port. Usually, the port is > 8080, not 8000. > Still not work. > image ( > https:/ / user-images. githubusercontent. > com/ 1861277/ 90635787-3c043a00-e25c-11ea-9a47-e2e3e6597421. png ( > https://user-images.githubusercontent.com/1861277/90635787-3c043a00-e25c-11ea-9a47-e2e3e6597421.png > ) > ) > image ( > https:/ / user-images. githubusercontent. com/ 1861277/ 90635823-4c1c1980-e25c-11ea-9d44-2ff9c23652d6. > png ( > https://user-images.githubusercontent.com/1861277/90635823-4c1c1980-e25c-11ea-9d44-2ff9c23652d6.png > ) > ) > > — You are receiving this because you commented. Reply to this > email directly, view it on GitHub ( #3680 (comment) ( > #3680 (comment) ) ) > , or unsubscribe ( https:/ / github. com/ notifications/ unsubscribe-auth/ > AAAIPOVBFOCPZIFIOQVDWUTSBPCBLANCNFSM4IEUQP2A ( > https://github.com/notifications/unsubscribe-auth/AAAIPOVBFOCPZIFIOQVDWUTSBPCBLANCNFSM4IEUQP2A > ) ). > > image ( https://user-images.githubusercontent.com/1861277/90636334-0744b280-e25d-11ea-9954-eef6002cfa8c.png ) — You are receiving this because you commented. Reply to this email directly, view it on GitHub ( #3680 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAIPOUZA6MC4P5AO54ZLELSBPCS3ANCNFSM4IEUQP2A ).
yes! it works : many thanks!
There is no need to click the login button here
if so remove it
@WolfgangFahl I have created a ticket for this and it is in the backlog https://discuss.dgraph.io/t/make-ee-features-optional-on-ui-hide-or-disable-acl-login/9540
@MichelDiz Please don't hide comments else where by moving to a different sytem. Hic Rhodos hic salta!
@WolfgangFahl Sorry, I'm not hiding, this is our new guideline. We won't give support or track anything on Github. That's beyond me. And actually, it doesn't make sense to open a bug Ticket in a reply comment.
PS. BTW, all issues on Github aren't being monitored. You should start topics/questions/issues at https://discuss.dgraph.io/
This comment above I had shared on my answer up there.
Cheers.
This has been fixed in master
I installed it on my server and trying to access port 8000 via my ip.. it is asking for password for user id "groot" .
WHATS THE PASSWORD?
@arsalan993 We have moved away from github issues, please ask your question on https://discuss.dgraph.io
IAC, dgraph doesn't launch with a password by default unless you've explicitly enabled ACL. If you have enabled ACL, the default password for groot is password
how to enable it in the community education.
From: Tejas Dinkar notifications@github.com Sent: Thursday, October 22, 2020 4:19 PM To: dgraph-io/dgraph dgraph@noreply.github.com Cc: Arsalan Ahmed arslan993@hotmail.com; Mention mention@noreply.github.com Subject: Re: [dgraph-io/dgraph] What is the default password? (#3680)
@arsalan993https://github.com/arsalan993 We have moved away from github issues, please ask your question on https://discuss.dgraph.io
IAC, dgraph doesn't launch with a password by default unless you've explicitly enabled ACL. If you have enabled ACL, the default password for groot is password
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/dgraph-io/dgraph/issues/3680#issuecomment-714423921, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFHYIGFMPTWK7ES7I3AYM6DSMAILZANCNFSM4IEUQP2A.
@gja says the default password for groot is password
But how to enable ACL?
$ dgraph alpha --my=alpha:7080 --zero=zero:5080 --acl
dgraph-alpha_1 | [Decoder]: Using assembly version of decoder
dgraph-alpha_1 | Error: unknown flag: --acl
version: "3.7"
services:
dgraph-zero:
image: dgraph/dgraph:v20.03.1
hostname: zero
volumes:
- dgraph:/dgraph
ports:
- 5080:5080
- 6080:6080
restart: on-failure
command: dgraph zero --my=dgraph-zero:5080
dgraph-alpha:
image: dgraph/dgraph:v20.03.1
hostname: alpha
links:
- "dgraph-zero:zero"
volumes:
- dgraph:/dgraph
ports:
- 8180:8080
- 9080:9080
restart: on-failure
command: dgraph alpha --my=alpha:7080 --zero=zero:5080
dgraph-ratel:
image: dgraph/dgraph:v20.03.1
hostname: ratel
ports:
- 8100:8000
command: dgraph-ratel
volumes:
dgraph:
@gja says the default password for groot is
password
But how to enable ACL?See this doc https://dgraph.io/docs/enterprise-features/access-control-lists/#enable-enterprise-acl-feature
Question is how to disable ACL. Not enterprise instance and ratel asks for ACL. Giving default password and it says enterprise is disable. Going to cluster section and it says You need to login as guardians group member to view Cluster State
I have no idea what is going on here
ACL is not enabled by default. You have the option to use it for 30 days to test and thats it. If it is aksing you for password that means you have started the cluster with the configs for ACL enabled. Just undo it.
@MichelDiz i didn't. Only what i changed is adding fake file to --enterprise_license
to be able run it in non-enterprise mode for tests and compare in my use-case. Trying this basing on my post here https://discuss.dgraph.io/t/turn-off-enterprise-features/18241/3 it is really weird there is no flag to turn it off
@rkozlo don't do this. When you use that flag you are saying that you have a license. Just don't change anything in the cluster and you are good to go. After 30 days all EE features are disabled. Which means Dgraph enter in "non-enterprise mode".
What was said in that post feels wrong. Anyway, whether the way Matthew mentions ever worked, I don't know. But the way I'm telling you is how Dgraph handles Enterprise expiration.
@MichelDiz thanks for reply. Just wanted to turn off to make most credible tests and benchmarks. It is a bit wird there is no flag to turn it off. Anyway I'll continue with this, so thanks again for help.
I setup dgraph using your docs - https://docs.dgraph.io/get-started
Then it says to connect to ratel to start running queries.
However, it won't connect at all. Everything is running fine according to docker logs.
There is some mention of a default password, but no mention of what that password is.
There are instructions on how to update the password using
dgraph acl
command but when I go into the console on the dgraph zero server and try to run that command, it saysunknown command "acl" for "dgraph"
.Are there any instructions for getting started that actually detail everything you need to do?
Why can't I set the default password via an environment variable similar to many other docker images?