On Mon, Mar 17, 2014 at 2:19 PM, oxsav <vmfamaral(a)gmail.com> wrote:
Hmm did it. And the problem persists.
I analysed the log from the jboss and when I try to open the URL:
http://150.140.184.246:4441/unifiedpush-server-0.10.0 , returns me the
following error:
/*5:07:49,969 ERROR [org.jboss.as.ejb3.invocation] (default task-1)
JBAS014134: EJB Invocation failed on component Ping for method public
javax.ws.rs.core.Response
org.jboss.aerogear.unifiedpush.rest.util.Ping.ping():
javax.ejb.EJBException:
org.jboss.aerogear.security.exception.AeroGearSecurityException: Not
authorized!*/
The first "Ping" Rest call will always return this, the admin client uses
this to check if you are connected or not. So, having this log (probably at
the beginning) make sense.
The weird thing is, I can access that well and create my application, my
variant and I already have an device registered to a variant :S ..
Any idea?
Again, sorry again for asking stupid questions but you are sure to not have
left the "{" and "}" around the PushId and the masterID, check this
valid
example :
https://github.com/sebastienblanc/chuckpush/blob/master/CURL.txt
Tks,
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-...
Sent from the aerogear-dev mailing list archive at
Nabble.com.
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev