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.

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

Getting 503 error #1356

Closed
mdrobb opened this issue Oct 9, 2023 · 2 comments
Closed

Getting 503 error #1356

mdrobb opened this issue Oct 9, 2023 · 2 comments
Labels
stale support Help, I'm stuck somehow

Comments

@mdrobb
Copy link

mdrobb commented Oct 9, 2023

Describe the issue

A clear and concise description of where you're stuck in the guide. What are you trying to do, and how is it not working?

Location in guide

Link to the corresponding page and section on https://raspibolt.org

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

  • Hardware platform: [e.g. Raspberry Pi 4, Odroid, ... ]
  • Operating system: [e.g, Raspberry Pi OS 64bit, Debian 11, ... ]
  • Version: [ output of lsb_release -d ]

Additional context

Add any other context about the problem here.

Oct 09 09:28:08 myNode bos[16638]: message: 503,UnexpectedErrorGettingCertFileData,[object Object]
Oct 09 09:28:08 myNode bos[16638]: stack:
Oct 09 09:28:08 myNode bos[16638]: - Error: 503,UnexpectedErrorGettingCertFileData,[object Object]
Oct 09 09:28:08 myNode bos[16638]: - at /home/bos/balanceofsatoshis/node_modules/async/asyncify.js:105:61
Oct 09 09:28:08 myNode systemd[1]: bos-telegram.service: Main process exited, code=killed, status=2/INT
Oct 09 09:28:08 myNode systemd[1]: bos-telegram.service: Succeeded.
Oct 09 09:28:39 myNode systemd[1]: bos-telegram.service: Service RestartSec=30s expired, scheduling restart.
Oct 09 09:28:39 myNode systemd[1]: bos-telegram.service: Scheduled restart job, restart counter is at 1046.

this is the error I'm seeing, debian/mynode

@mdrobb mdrobb added the support Help, I'm stuck somehow label Oct 9, 2023
Copy link

github-actions bot commented Dec 8, 2023

This issue is marked as stale because there was no activity for 60 days. If the issue stays inactive, it will be closed in a week.

@github-actions github-actions bot added the stale label Dec 8, 2023
Copy link

This issue has been closed due to inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale support Help, I'm stuck somehow
Projects
None yet
Development

No branches or pull requests

1 participant