This was a bug I fixed yesterday: the console converted the localhost to
the public IP. It's fixed in v2.2.x branch.
Have you read the issue and its comments?
Founder & CEO
OrientDB LTD <http://orientdb.com/>
Want to share your opinion about OrientDB?
Rate & review us at Gartner's Software Review
On 22 September 2016 at 18:39, William <wcmc...@gmail.com> wrote:
> Sorry, I'm not sure I'm following you. I changed the only listener ip
> address locations that I can find in the entire configuration directory to
> 127.0.0.1... it's only on the two lines in orientdb-server-config.xml as I
> referenced... but console ignores that.
> Can you provide more detail? Is there a different file that I need to
> edit? Is there a new element that needs to be added to the configuration
> XML file?
> On Thursday, September 22, 2016 at 5:06:19 PM UTC-6, Ivan Mainetti wrote:
>> in the listener configuration ip-address you need to insert the allowed
>> source ip, for example if you want to allow only connection from your
>> machine you need to insert your actual ip of net interface not the loopback
>> one (127.0.0.1).
>> Hope this is clear.
>> Il giorno venerdì 23 settembre 2016 00:31:40 UTC+2, William ha scritto:
>>> Can anyone confirm this behavior... I'm not sure if it's a bug or if I'm
>>> just doing something wrong...
>>> I noticed yesterday that when I fire up the server.sh application, the
>>> default behavior is to listen on an outward facing port on my machine...
>>> 2016-09-22 16:08:35:815 INFO OrientDB Studio available at http://<MY
>>> ACTUAL IP ADDRESS>:2480/studio/index.html [OServer]
>>> Since our cybersecurity department at my organization frowns upon firing
>>> up servers that listen to outward facing ports, I modified the
>>> <listeners> section in config/orientdb-server-config.xml file
>>> <listener protocol="binary" socket="default"
>>> port-range="2424-2430" ip-address="*0.0.0.0*"/>
>>> <listener protocol="http" socket="default"
>>> port-range="2480-2490" ip-address="*0.0.0.0*">
>>> so that the ip-address field is "127.0.0.1".
>>> I can connect Studio to the database using 127.0.0.1:2480 or
>>> localhost:2480 and everything works fine. I verified that
>>> http://my-machine-name:2480/ will correctly fail too. I hit a problem
>>> though when I try to use the console application.
>>> I get the following behaviour in console.sh:
>>> *$* *console.sh*
>>> OrientDB console v.2.2.10 (build
>>> 2016-09-15 08:47:27+0000) www.orientdb.com
>>> Type 'help' to display all the supported commands.
>>> Installing extensions for GREMLIN language v.2.6.0
>>> *orientdb>* connect REMOTE:localhost/myDatabase admin admin
>>> Connecting to database [REMOTE:localhost/myDatabase] with user 'admin'...
>>> Error: com.orientechnologies.orient.core.exception.OStorageException:
>>> Cannot create a connection to remote server address(es): [<SYSTEM IP
>>> DB name="myDatabase"
>>> Based on what I can see in the documentation
>>> <http://orientdb.com/docs/last/Console-Command-Connect.html> I would
>>> think that this should work. I've tried using REMOTE:localhost/myDatabase
>>> and REMOTE:127.0.0.1/myDatabase but the result is the same... OrientDB
>>> appears to completely ignore my instructions and runs with its default and
>>> tries to connect to my machine's real IP address.
>>> Is this a bug or is there something that I am missing?
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.