Skip to content

bug:Light push works only when client & service node lightpush=true #1253

@AYAHASSAN287

Description

@AYAHASSAN287

Describe the bug
When Node wants to send message to 1 peer using lightpush , both client & receiving node needs to have lightpush = true

To Reproduce
Steps to reproduce the behavior:
1- Create node1 with lightpush = true // relay = true // store = true [go-waku]
2 Create node2 with relay = true // store = true // discov5 = node1_ip_address [nim=waku]
3- Create node3 with relay = false // discov5=node1_ip_address // choose node1 as "lightpushnode" [nim-waku]
3-Node3 send a message using lightpush protocol

Expected behavior
Message sent to node1 and node1 forward it on relay to node2

Actual behavior

fails to send the message and got error "Server Error: Service Unavailable for url: http://127.0.0.1:29443/lightpush/v1/message with response: b'Failed to request a message push: "

go-waku version/commit hash

Test done using REST APIs

Additional context
Issue doesn't appear if node3 = go-waku and node1 peer = nwaku
Issue doesn't appear if node1 = go-waku and node3 = go-waku

Note: Node2 could be removed and behavior is the same

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions