# Can not connect to ASL3 node

**URL:** <https://community.allstarlink.org/t/can-not-connect-to-asl3-node/23105>\
**Category:** AllStarLink\
**Tags:** asl3\
**Created:** [April 2, 2025, 6:49pm UTC](https://community.allstarlink.org/t/can-not-connect-to-asl3-node/23105 "2025-04-02T18:49:17Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [April 3, 2025, 10:22am UTC](https://community.allstarlink.org/t/can-not-connect-to-asl3-node/23105/5 "2025-04-03T10:22:51Z")

</div>

There are a lot of things that could be at issue here, but lets start with the stupid stuff.  
Here is a common list I made you can look at.  
[The 5 most popular reasons for connection failure](https://community.allstarlink.org/t/the-5-most-popular-reasons-for-connection-failure/22178)

Now, one thing that stands out as a possibility that should be eliminated is loopback protection. Public or private node(s).

If your node A is connected to node (any#) and your other node B is connected to the same, you will not be able to connect the 2 nodes of yours ( A & B ) together.

But it might help to watch asterisk commands in the foreground to see if the connection attempts are reporting.

```auto
asterisk -rvvv

```

---

_[View the full topic](https://community.allstarlink.org/t/can-not-connect-to-asl3-node/23105)._