# Subscription with Wildcards

**URL:** <https://community.hivemq.com/t/subscription-with-wildcards/313>\
**Category:** HiveMQ Community Edition\
**Created:** [August 21, 2020, 6:37pm UTC](https://community.hivemq.com/t/subscription-with-wildcards/313 "2020-08-21T18:37:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![brunojesus](https://avatars.discourse-cdn.com/v4/letter/b/f6c823/32.png) [@brunojesus](https://community.hivemq.com/u/brunojesus)\
**Post date:** [August 21, 2020, 6:37pm UTC](https://community.hivemq.com/t/subscription-with-wildcards/313/1 "2020-08-21T18:37:01Z")

</div>

Hi guys, sorry for the newbie question, but I’m having a problem with wildcards. I’m trying to subscribe on HiveMQ broker with topic +/# and publishing with the command

mosquitto\_pub -h [broker.hivemq.com](http://broker.hivemq.com) -t sensors/DHT -m “Test from RP HIVEMQ” -d -r

obtaining this result:

$ sudo mosquitto\_sub -h [broker.hivemq.com](http://broker.hivemq.com) -t +/# -d  
Client mosq-PdLPJRoLkptWR5tW5D sending CONNECT  
Client mosq-PdLPJRoLkptWR5tW5D received CONNACK (0)  
Client mosq-PdLPJRoLkptWR5tW5D sending SUBSCRIBE (Mid: 1, Topic: +/#, QoS: 0, Options: 0x00)  
Client mosq-PdLPJRoLkptWR5tW5D received SUBACK  
Subscribed (mid: 1): 128  
Client mosq-PdLPJRoLkptWR5tW5D sending PINGREQ  
Client mosq-PdLPJRoLkptWR5tW5D received PINGRESP

But, when I do the same procedure on my local broker, I got the results. There is some kind of block on hiveMQ for this kind of subscription with wildcards?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![michael\_w](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/michael_w/32/200_2.png) [@michael\_w](https://community.hivemq.com/u/michael_w)\
**Post date:** [August 22, 2020, 7:22pm UTC](https://community.hivemq.com/t/subscription-with-wildcards/313/2 "2020-08-22T19:22:06Z")

</div>

Hi @brunojesus,

our public HiveMQ broker (`broker.hivemq.com`) doesn’t allow any kind of “full wildcard”.  
You can subscribe to “test/#” but not to “+/#”.

You should not have this problem with your local broker.

Greetings,  
Michael from the HiveMQ team

---

<div class="post-metadata">

**Author:** ![FloLi](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/floli/32/17_2.png) [@FloLi](https://community.hivemq.com/u/FloLi)\
**Post date:** [August 24, 2020, 10:36am UTC](https://community.hivemq.com/t/subscription-with-wildcards/313/3 "2020-08-24T10:36:44Z")

</div>

Hi brunojesus,

> [@brunojesus](#):
>
> Client mosq-PdLPJRoLkptWR5tW5D received SUBACK  
> Subscribed (mid: 1): 128

Your client tells you that the subscribe failed by the returncode “128” (Unspecified Error).  
If the subscribe was successful then the returncode would return 0,1 or 2 depending on the granted QoS level.