Antsle Forum

Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more. 

Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked. 

You need to log in to create posts and topics.

Can't connect via local IP

I have no problem connecting to my antsle via antslename.local, but trying to connect with the IP gives me an nginx 403 error. Obviously something isn't configured properly, but what?

Craig

You are adding port 3000 to get to antMan correct?
Example: antsle ip = 192.168.0.120

To get to antMan type in browser: http://192.168.0.120:3000

I was not adding port 3000; doing so works with the IP. It does not, however, work with our antsle.us domain; instead that takes me to an Anthill login screen. (Without the port it takes me to the same nginx 403 page as the IP without the port.)

Edit: Anthill, not Antman

Hmmm if you subdomain is say bones you should be able to access antMan via https://bones.antsle.us at least from your local network. But you are getting then 403 nginx error instead?

Actually, I just retested in Chrome and it works fine. Safari is giving the 403 problem.

Interesting. OK I'll test it here and see if I can get ones of the devs to look at it. Thanks!

powered by proof factor - increase conversions with social proof notifications