Skip to content

Bug: Reistration New We're sorry, but something went wrong. #2067

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

Open
4 tasks
blakeusblade opened this issue Apr 8, 2025 · 0 comments
Open
4 tasks

Bug: Reistration New We're sorry, but something went wrong. #2067

blakeusblade opened this issue Apr 8, 2025 · 0 comments

Comments

@blakeusblade
Copy link

blakeusblade commented Apr 8, 2025

Before you start (required)

General checklist

  • [ X ] I have removed personal / sensitive data from screenshots and logs
  • [ X ] I have searched existing issues and discussions to ensure this is not a duplicate issue

How are you using Maybe?

  • I am a paying Maybe customer (hosted version)
    • Paying Maybe users can also open requests in Intercom (if there is sensitive info involved)
  • [ X ] I am a self-hosted user

Self hoster checklist

Paying, hosted users should delete this entire section.

If you are a self-hosted user, please complete all of the information below. Issues with incomplete information will be marked as Needs Info to help our small team prioritize bug fixes.

  • Self hosted app commit SHA (find in user menu): [enter commit sha here]
    • [ X ] I have confirmed that my app's commit is the latest version of Maybe
  • Where are you hosting?
    • Render
    • [ X ] Docker Compose / Portainer
    • Umbrel
    • Other (please specify)

Bug description

When attempting to navigate to the URL for the first time upon inital startup, it throw "We're sorry, but something went wrong."

Image

logs
I, [2025-04-08T02:04:01.426806 #1] INFO -- : {message: "Started GET "/registration/new"", event: {http_request_received: {body: nil, content_length: nil, headers_json: "{"Connection":"close","Host":"maybe.mydomain.on.net","X_Real_Ip":"10.78.36.158","X_Forwarded_For":"10.78.36.158","X_Forwarded_Proto":"https","Cache_Control":"max-age=0","Sec_Ch_Ua":"\"Chromium\";v=\"134\", \"Not:A-Brand\";v=\"24\", \"Google Chrome\";v=\"134\"","Sec_Ch_Ua_Mobile":"?0","Sec_Ch_Ua_Platform":"\"Windows\"","Dnt":"1","Upgrade_Insecure_Requests":"1","User_Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36","Accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7","Sec_Fetch_Site":"none","Sec_Fetch_Mode":"navigate","Sec_Fetch_User":"?1","Sec_Fetch_Dest":"document","Accept_Encoding":"gzip, deflate, br, zstd","Accept_Language":"en-US,en;q=0.9","Priority":"u=0, i","Version":"HTTP/1.1","X_Forwarded_Port":"443"}", host: "maybe.mydomain.on.net", method: "GET", path: "/registration/new", port: 443, query_string: "", request_id: "60a7cdd8-3975-4e4a-a758-7b3c8b93ccd5", scheme: "https", service_name: nil}}}

I, [2025-04-08T02:04:01.428238 #1] INFO -- : Processing by RegistrationsController#new as HTML
I, [2025-04-08T02:04:01.442344 #1] INFO -- : Rendered registrations/new.html.erb within layouts/auth (9.3ms)
F, [2025-04-08T02:04:01.454961 #1] FATAL -- : ActionView::Template::Error (failed to get urandom)

To Reproduce

Be as specific as possible so Maybe maintainers can quickly reproduce the bug you're experiencing.

Steps to reproduce the behavior:

Following these steps exactly using portainer
https://mariushosting.com/how-to-install-maybe-on-your-synology-nas/

Expected behavior

The registration page being displayed

Screenshots and/or recordings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant