#A4M1N - terminal

1 messages · Page 1 of 1 (latest)

ancient ice
#

Hi there. One moment

acoustic pond
#

Sure

ancient ice
#

What guide are you following?

acoustic pond
#

Any luck...

ancient ice
#

Let me ask a colleague

faint kindle
#

Hi 👋 I'm jumping in to provide some more info here.

#

Have you been able to connect your reader to a local wifi network?

acoustic pond
#

Yes, and it gets IP address

faint kindle
#

Okay and the readers are able to update from the network?

acoustic pond
#

yes they do

faint kindle
#

Okay and you are trying to connect and/or ping these readers from a machine on the same local network I am assuming.

acoustic pond
#

No from another network.. But I can do locally if needed

faint kindle
#

Both the machine and the device need to be on the same local network

acoustic pond
#

ok let me try now

faint kindle
#

Also can you try running nslookup 192-168-0-15.5ppefnley7mgvpcmz4fe.device.stripe-terminal-local-reader.net

acoustic pond
#

So is this an API based or Local ?

#

would it work on Local only ?

faint kindle
#

Well ping or ns lookup will only work on the same network.

#

Unless you are using server driver integration, the POS and the reader will need to be on the same local network

#

Are you able to reach the reader now?

acoustic pond
#

Trying on local one moment plz

#

Hello

#

As you can see we are connected on same local but still not ping able

#

can I give you access to the system on local network so you can have a look at it yourself plz

slender oyster
#

Hello! I'm taking over and catching up...

#

Ah, that's not how the ping command works. You need to ping either the IP address or the hostname. Let's start with pinging the IP address. Try this command: ping 192.168.86.197

#

Let me know what happens when you try that and we'll go from there.

acoustic pond
#

sent 4 received 4 lost 0

#

works fine

#

@slender oyster

slender oyster
#

Okay, so pinging the hostname didn't work, which indicates a DNS issue. Can you try nslookup with the hostname?

acoustic pond
#

same result

slender oyster
#

Okay, will you try the same nslookup command but add 1.1.1.1 at the end? So it's like this: nslookup <hostname> 1.1.1.1 and see if that works?

acoustic pond
#

Not unfortunately

slender oyster
#

Oh, sorry, I didn't mean for you to include the < and > characters.

#

That was just to indicate it was a placeholder.

acoustic pond
#

any chance I can give you anydesk

slender oyster
#

If you paste the hostname in here I can give you the exact command to run.

#

I don't know what anydesk is, but if it's some kind of remote screen sharing tool then no, sorry, I can't use anything like that.

acoustic pond
slender oyster
#

nslookup 192-168-86-197.5ppefnley7mgvpcmz4fe.device.stripe-terminal-local-reader.net 1.1.1.1

#

Try that command and see if you can resolve the hostname with that DNS server.

acoustic pond
#

@slender oyster

slender oyster
#

Okay, so that works. If you change your system's DNS servers to 1.1.1.1 and 1.0.0.1 and then try Terminal again does it work as expected?

acoustic pond
slender oyster
#

Okay, cool. So if you try your Terminal integration again does it work?

acoustic pond
#

not unfortunately still problem

slender oyster
#

That's a new issue; your Terminal integration is running in an insecure context, which you need to fix before it will work.

#

See the "Not secure" in the top left?

acoustic pond
#

sure then I will get the ssl certificate sorted tomorrow and try again

#

if come across new issue will give you a shout

#

you been a great help

#

thanks so much

slender oyster
#

Sounds good! I think you're almost there. 🙂