Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Relay operator for mobile notifications #82

Open
ManfredKarrer opened this issue Mar 19, 2019 · 56 comments
Open

Relay operator for mobile notifications #82

ManfredKarrer opened this issue Mar 19, 2019 · 56 comments
Assignees
@devinbileck
Labels
team:ops https://bisq.wiki/Ops_Team

Comments

@ManfredKarrer
Copy link
Member

ManfredKarrer commented Mar 19, 2019 •
edited
Loading

Running the relay node used for mobile notifications.

Primary owner: @devinbileck
@ManfredKarrer ManfredKarrer self-assigned this Mar 19, 2019
devinbileck added a commit to devinbileck/bisq that referenced this issue Apr 23, 2019
@devinbileck
Update mobile notification relay node DEV_URL IP address
5fb08f8 
I have taken over the relay node from Manfred. The onion address
remains the same, but the IP address used in the DEV_URL has
changed.

See bisq-network/roles#82
@devinbileck devinbileck mentioned this issue Apr 23, 2019
Merged
@devinbileck devinbileck mentioned this issue May 3, 2019
Closed
@devinbileck
Copy link
Member

devinbileck commented May 3, 2019 •
edited
Loading

2019.04 report

I have setup and transferred ownership of the jtboonrvwmq7frkj.onion relaynode from @ManfredKarrer (bisq-network/bisq#2770).

While attempting to setup/run the relay node, I was encountering Error while calling FCM backend service when relaying Android notifications and no Android notifications were being relayed. However, iOS notifications work fine.

Unfortunately, this issue wasn't identified until after I had already made the transition and my node was the primary relay. As a result, for several hours on April 24/25 Android notifications were not being relayed. During my testing prior to the transition, I had just tested iOS notifications and assumed the relay was functioning correctly since I did not have access to an Android device at the time to verify.

At this point, the issue seems to be due to compiling under the new mono repo using Java 10. Whereas using the old bisq-relay repo and compiling with Java 8, Android notifications work fine. So for now, my relay is using the old repo with Java 8.

An issue has been entered for this, see bisq-network/bisq#2791.

Expenses incurred for the month (USD):

  • $10 for server (1 CPU, 2GB)

Note: Although the transition did not occur until towards the end of the month, my server was running since the beginning of the month in preparation/anticipation of the transition.

/cc bisq-network/compensation#270

@devinbileck devinbileck mentioned this issue Jun 7, 2019
Closed
@devinbileck
Copy link
Member

2019.05 report

Running 1 relaynode.

  • jtboonrvwmq7frkj.onion

No issues to report this month.

No maintenance required this month.

Expenses incurred for the month (USD):

  • $10 for server (1 CPU, 2 GB RAM)

/cc bisq-network/compensation#295

@devinbileck
Copy link
Member

Cycle 3 report

Summary

Running 1 relay node for mobile notifications, nothing notable happened this month.

  • jtboonrvwmq7frkj.onion

Issues Encountered

No issues encountered this month.

Maintenance Performed

No maintenance performed this month.

Expenses Incurred

Expenses incurred for the month (USD):

  • $10 for server (1 CPU, 2 GB RAM)

/cc bisq-network/compensation#309

@devinbileck devinbileck mentioned this issue Jul 8, 2019
Closed
@devinbileck devinbileck mentioned this issue Aug 8, 2019
Closed
@devinbileck
Copy link
Member

Cycle 4 report

Summary

Running 1 relay node for mobile notifications, nothing notable happened this month.

  • jtboonrvwmq7frkj.onion

Issues Encountered

No issues encountered this month.

Maintenance Performed

No maintenance performed this month.

Expenses Incurred

Expenses incurred for the month (USD):

  • $10 for server (1 CPU, 2 GB RAM)

/cc bisq-network/compensation#326

@devinbileck devinbileck mentioned this issue Sep 9, 2019
Closed
@devinbileck
Copy link
Member

Cycle 5 report

Summary

Running 1 relay node for mobile notifications, nothing notable happened this month.

  • jtboonrvwmq7frkj.onion

Issues Encountered

No issues encountered this month.

Maintenance Performed

No maintenance performed this month.

Expenses Incurred

Expenses incurred for the month (USD):

  • $10 for server (1 CPU, 2 GB RAM)

/cc bisq-network/compensation#353

@devinbileck devinbileck mentioned this issue Oct 9, 2019
Closed
@devinbileck
Copy link
Member

Cycle 6 report

Summary

Running 1 relay node for mobile notifications.

  • jtboonrvwmq7frkj.onion

Issues Encountered

On Sept 12th, iOS notifications stopped working due to an expired Apple push certificate. I was made aware of the issue from this forum post. It took a couple days to resolve the issue, but I acquired and deployed a new certificate with the help of @joachimneumann who manages the app and certificates. Apparently an email was received from Apple 30 days prior to it expiring, but it was not acted upon. The new certificate will expire on 2020/10/13, so hopefully we will act to renew it in time before it expires again.

Maintenance Performed

No maintenance performed this month, aside from updating the Apple push certificate.

Expenses Incurred

Expenses incurred for the month (USD):

  • $10 for server (1 CPU, 2 GB RAM)

/cc bisq-network/compensation#378

@devinbileck devinbileck mentioned this issue Nov 11, 2019
Closed
@devinbileck
Copy link
Member

Cycle 7 report

Summary

Running 1 relay node for mobile notifications.

  • jtboonrvwmq7frkj.onion

Issues Encountered

No issues encountered.

Maintenance Performed

No maintenance performed.

Expenses Incurred

Expenses incurred for the month (USD):

  • $10 for server (1 CPU, 2 GB RAM)

/cc bisq-network/compensation#400

@devinbileck devinbileck mentioned this issue Dec 13, 2019
Closed
@devinbileck
Copy link
Member

Cycle 8 report

Summary

Running 1 relay node for mobile notifications.

  • jtboonrvwmq7frkj.onion

Issues Encountered

None.

Maintenance Performed

None.

Requested Compensation

  • 10 USD for server costs (1 CPU, 2 GB RAM)
  • 50 USD to ensure 24/7 trouble-free operation

Total: 60 USD

/cc bisq-network/compensation#437

@devinbileck devinbileck mentioned this issue Jan 14, 2020
Closed
@devinbileck
Copy link
Member

Cycle 9 report

Summary

Running 1 relay node for mobile notifications.

  • jtboonrvwmq7frkj.onion

Issues Encountered

None.

Maintenance Performed

None.

Requested Compensation

  • 10 USD for server costs (1 CPU, 2 GB RAM)
  • 50 USD for maintenance/operational costs

Total: 60 USD

/cc bisq-network/compensation#472

@devinbileck devinbileck mentioned this issue Feb 8, 2020
Closed
@devinbileck
Copy link
Member

Cycle 10 report

Running 1 instance.
Lately I have heard iOS users are encountering issues with the mobile app being unable to decrypt messages, in addition to issues around pairing. While I dont think this is due to the relay, I am still planning to investigate the issue.

/cc bisq-network/compensation#481

@devinbileck devinbileck mentioned this issue Mar 11, 2020
Closed
@devinbileck
Copy link
Member

Cycle 11 report

Running 1 instance.
I have not had time yet to investigate the above mentioned issue.

/cc bisq-network/compensation#512

@devinbileck devinbileck mentioned this issue Apr 13, 2020
Closed
@devinbileck devinbileck mentioned this issue Feb 8, 2023
Closed
@devinbileck
Copy link
Member

Cycle 44 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1234

@devinbileck devinbileck mentioned this issue Mar 10, 2023
Closed
@devinbileck
Copy link
Member

Cycle 45 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1253

@devinbileck devinbileck mentioned this issue Apr 11, 2023
Closed
@devinbileck
Copy link
Member

Cycle 46 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1277

@devinbileck devinbileck mentioned this issue May 13, 2023
Closed
@devinbileck
Copy link
Member

Cycle 47 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1294

@devinbileck devinbileck mentioned this issue Jun 16, 2023
Closed
@devinbileck
Copy link
Member

Cycle 48 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1318

@devinbileck devinbileck mentioned this issue Jul 19, 2023
Closed
@devinbileck
Copy link
Member

Cycle 49 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1342

@devinbileck devinbileck mentioned this issue Aug 18, 2023
Closed
@devinbileck
Copy link
Member

Cycle 50 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1354

@devinbileck devinbileck mentioned this issue Sep 19, 2023
Closed
@devinbileck devinbileck mentioned this issue Oct 21, 2023
Closed
@devinbileck devinbileck mentioned this issue Nov 20, 2023
Closed
@devinbileck devinbileck mentioned this issue Dec 24, 2023
Closed
@devinbileck devinbileck mentioned this issue Jan 25, 2024
Closed
@devinbileck
Copy link
Member

Cycle 55 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1472

@devinbileck devinbileck mentioned this issue Feb 24, 2024
Closed
@devinbileck
Copy link
Member

Cycle 56 report

Running 1 instance.
Nothing to report.

/cc bisq-network/compensation#1490

@devinbileck devinbileck mentioned this issue Mar 26, 2024
Closed
@devinbileck
Copy link
Member

Cycle 57 report

Running 1 instance.
Updated to this PR.

/cc bisq-network/compensation#1507

@devinbileck devinbileck mentioned this issue Aug 5, 2024
Open
@devinbileck
Copy link
Member

Cycle 61 report

Continuing to run the node.
Nothing to report.

/cc bisq-network/compensation#1594

@devinbileck devinbileck mentioned this issue Sep 5, 2024
Open
@devinbileck
Copy link
Member

Cycle 62 report

Continuing to run the node.
Nothing to report.

/cc bisq-network/compensation#1611

@devinbileck devinbileck mentioned this issue Oct 9, 2024
Open
@devinbileck
Copy link
Member

Cycle 63 report

Continuing to run the node.
Nothing to report.

/cc bisq-network/compensation#1635

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

@devinbileck devinbileck

Labels
team:ops https://bisq.wiki/Ops_Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cbeams @devinbileck @ManfredKarrer