Skip to content

Feedback url is not receiving #813

Description

@sanjaylakum7

I am currently experiencing an issue with Gorush feedback URL configuration. Despite successfully receiving push notifications and responses in the console log, no response is being sent to the specified feedback_hook_url.

Core Configuration:

core:
  feedback_hook_url: "https://example.com/notification-response/feedback-url/"
  feedback_timeout: 10
  feedback_header:
    - x-gorush-token: 12345
  mode: "release"
  ssl: false
  cert_path: "cert.pem"
  key_path: "key.pem"
  cert_base64: ""
  key_base64: ""
  http_proxy: ""
  pid:
    enabled: false
    path: "gorush.pid"
    override: true
  auto_tls:
    enabled: false
    folder: ".cache"
    host: ""


# Request body
curl --location 'http://localhost:8088/api/push' \
--data '{
    "notifications": [
        {
            "tokens": [
                "Token1"
            ],
            "platform": 2,
            "message": "This is my msg"
        }
    ]
}'

Problem:

Expected behavior: The response should be sent to the configured feedback_hook_url.
Actual behavior: No response is being sent to the feedback_hook_url. However, the response is being logged in the console.

Additional Information:

  • The core is running in release mode.
  • SSL is disabled.
  • Feedback headers are properly configured with a token.

Activity

  1. HrachMD commented on Nov 16, 2024

    @HrachMD

    Same for me. FeedbackURL never being called.

  2. HrachMD commented on Nov 16, 2024

    @HrachMD

    Could you access to stats or metrics endpoints? In my case they are returning an empty response body.

  3. appleboy commented on Dec 11, 2024

    @appleboy
    Owner

    I will take it.

  4. self-assigned this
    on Dec 11, 2024
  5. obuzyig commented on Jan 2, 2025

    @obuzyig

    Hello everyone, in my case I have experienced that, during sending a couple of thousand Push Notifications, I could not get some feedback errors to the feedback url. It is minimal. Generally the case results in {1;2;3} lost feedbacks of {15000;30000}

    Throughout the sendings, I use the same token and expecting it returns with a generic error.

    This, using the same token with bulk sending, may also be causing to the such kind of a case.

    Is there anyone experienced such kind of a case or with recommendations?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions