starred/healthchecks

Fork 0

mirror of https://github.com/healthchecks/healthchecks.git synced 2026-04-25 15:05:49 +03:00

[GH-ISSUE #192] Registration - Email me a link- Incorrect email address #138

New issue

Closed

opened 2026-02-25 23:41:19 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:41:19 +03:00

Owner

Originally created by @red-erik on GitHub (Oct 17, 2018).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/192

Hi,
Great job so, first of all, thanks.
Email are working and I'm able to invite other users but the registration process always return "Incorrect Email Address".
REGISTRATION_OPEN = True
but no one is able to register and receive a link.
Another thing is that the admin page has no different option from the standard one. Witch is it's purpose ?
Regards.

Red.

Originally created by @red-erik on GitHub (Oct 17, 2018). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/192 Hi, Great job so, first of all, thanks. Email are working and I'm able to invite other users but the registration process always return "Incorrect Email Address". REGISTRATION_OPEN = True but no one is able to register and receive a link. Another thing is that the admin page has no different option from the standard one. Witch is it's purpose ? Regards. Red.

kerem closed this issue

2026-02-25 23:41:19 +03:00

kerem commented

2026-02-25 23:41:19 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 17, 2018):

Hi,

When you get the "Incorrect Email Address", are you on the /accounts/login/ page?
If so, the forms there don't handle new user registration. They only do login for already existing users.

To register as a new user, go to the front page ("/") and click on "Sign Up – It's Free" button – it should open a "Create Your Account" dialog:

@cuu508 commented on GitHub (Oct 17, 2018): Hi, When you get the "Incorrect Email Address", are you on the /accounts/login/ page? If so, the forms there don't handle new user registration. They only do login for already existing users. To register as a new user, go to the front page ("/") and click on "Sign Up – It's Free" button – it should open a "Create Your Account" dialog: ![image](https://user-images.githubusercontent.com/661859/47085218-9f675000-d21e-11e8-8c1e-c6d9623169a0.png)

kerem commented

2026-02-25 23:41:19 +03:00

Author

Owner

@red-erik commented on GitHub (Oct 17, 2018):

Hi,
You are (as usual) right, the signup on the home page works fine. Sorry for my mistake.
would you be so kind to explain me how to run the server with multiple parameters ?
To have it running I need to use ./manage.py runserver 0.0.0.0:8000 (otherwise it will respond to 127.0.0.1 only) but to receive alerts I need to use ./manage.py sendalerts.
How can I combine both without errors related to arguments?!?
Thank You in advance.

Regards.

Red.

@red-erik commented on GitHub (Oct 17, 2018): Hi, You are (as usual) right, the signup on the home page works fine. Sorry for my mistake. would you be so kind to explain me how to run the server with multiple parameters ? To have it running I need to use ./manage.py runserver 0.0.0.0:8000 (otherwise it will respond to 127.0.0.1 only) but to receive alerts I need to use ./manage.py sendalerts. How can I combine both without errors related to arguments?!? Thank You in advance. Regards. Red.

kerem commented

2026-02-25 23:41:19 +03:00

Author

Owner

@cuu508 commented on GitHub (Oct 17, 2018):

For development, I just run them in two separate console windows.
For production, it's a good idea to use uwsgi or gunicorn instead of the "./manage.py runserver".

With uwsgi, one option is to use "--attach-daemon" configuration directive. As a starting point, drop the following uwsgi.ini in your project directory:

[uwsgi]
http-socket = :8000
enable-threads
plugin = python3
module = hc.wsgi:application
static-map = /static=static-collected
static-gzip-dir = static-collected/CACHE
attach-daemon = ./manage.py sendalerts

And run uwsgi like so:

uwsgi --ini uwsgi.ini

uwsgi will start a sendalerts subprocess on startup, and will kill it on exit.

On https://healthchecks.io I run the sendalerts command separately, as a systemd service. This way I can start and stop the web server and the background processes individually. The .service file I'm using is:

[Unit]
Description=sendalerts
After=network-online.target
Wants=network-online.target

[Service]
Slice=machine.slice
Restart=always
RestartSec=20
StartLimitInterval=10
StartLimitBurst=5

User=www-data
Group=www-data

ExecStart=/usr/bin/python3 -u /path/to/healthchecks/manage.py sendalerts --no-threads

PrivateDevices=true
ProtectHome=true
ProtectSystem=full

[Install]
WantedBy=multi-user.target

@cuu508 commented on GitHub (Oct 17, 2018): For development, I just run them in two separate console windows. For production, it's a good idea to use uwsgi or gunicorn instead of the "./manage.py runserver". With uwsgi, one option is to use "--attach-daemon" configuration directive. As a starting point, drop the following `uwsgi.ini` in your project directory: ``` [uwsgi] http-socket = :8000 enable-threads plugin = python3 module = hc.wsgi:application static-map = /static=static-collected static-gzip-dir = static-collected/CACHE attach-daemon = ./manage.py sendalerts ``` And run uwsgi like so: uwsgi --ini uwsgi.ini uwsgi will start a sendalerts subprocess on startup, and will kill it on exit. On https://healthchecks.io I run the sendalerts command separately, as a systemd service. This way I can start and stop the web server and the background processes individually. The .service file I'm using is: ``` [Unit] Description=sendalerts After=network-online.target Wants=network-online.target [Service] Slice=machine.slice Restart=always RestartSec=20 StartLimitInterval=10 StartLimitBurst=5 User=www-data Group=www-data ExecStart=/usr/bin/python3 -u /path/to/healthchecks/manage.py sendalerts --no-threads PrivateDevices=true ProtectHome=true ProtectSystem=full [Install] WantedBy=multi-user.target ```

kerem commented

2026-02-25 23:41:19 +03:00

Author

Owner

@red-erik commented on GitHub (Oct 17, 2018):

Thank You very much for this explanation. I already created a service for for ./manage.py runserver 0.0.0.0:8000. Now I'll try to create a second service using your suggestion.
Great software and thank You again for sharing.
Regards.

Red.

@red-erik commented on GitHub (Oct 17, 2018): Thank You very much for this explanation. I already created a service for for ./manage.py runserver 0.0.0.0:8000. Now I'll try to create a second service using your suggestion. Great software and thank You again for sharing. Regards. Red.