Navigation

    webhookie

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    After setting up a subscription, http://localhost:4300/subscriptions/consumer is not accessable

    Technical Support
    2
    5
    151
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tanghuyin last edited by

      Will return this popup message

      Http failure response for http://localhost:4300/api/subscriptions?role=CONSUMER&size=20&page=0: 500 Internal Server Error

      L 1 Reply Last reply Reply Quote 0
      • L
        liam @tanghuyin last edited by liam

        @tanghuyin sorry to hear you are getting this issue. We've tried to replicate but cannot. Are you running webhookie using docker? Can you provide more details on how you replicated this issue? Also what would help would be the log files from your console, the docker compose file you are using and any other details you think would help.

        If the issue is localized to the subscriptions page can you provide details on the subscription you created? It may be something to do with some of the characteristics of that subscription that is causing the issue and will help us replicate it.

        If you are using the default docker-compose file then you can provide the subscription details in json by issuing the following commands in your command line:

        1. docker exec -it <mongo container id> mongo
        2. use webhookie-db
        3. db.subscription.find()
          You can find the mongo container id using the command docker ps

        If you don't want to post your subscription details here please send them to info(at)webhookie(dot)com (feel free to obfuscate any details but keep the characteristics the same).

        L 1 Reply Last reply Reply Quote 0
        • L
          liam @liam last edited by

          @tanghuyin did you resolve this issue as well? If you can please update the thread with any details of the issue?

          T 1 Reply Last reply Reply Quote 0
          • T
            tanghuyin @liam last edited by

            @liam The error log said that something required not null is null in the mongo. I manually delete the mongo data for subscription and create it again, it just solved. I may not find the cause but it is resolved! Thank you

            L 1 Reply Last reply Reply Quote 0
            • L
              liam @tanghuyin last edited by

              @tanghuyin ok, thanks for updating the thread. I'll move the thread to the Technical support category for future reference

              1 Reply Last reply Reply Quote 0
              • First post
                Last post