Guide for self hosting wakapi on AWS EC2

[palash-sarate]

config.yml.txt
wakapi.service.txt

attached is my attempt for self hosting the wakapi on an ec2 instance of AWS. i have created a service for wakapi but with attached config i get error

Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.80983168Z [INFO ] no need to migrate '20210806-remove_persisted_project_labels'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.809913283Z [INFO ] potentially running migration '20211215-migrate_id_to_bigint-add_has_data_field'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.8100554Z [INFO ] no need to migrate '20211215-migrate_id_to_bigint-add_has_data_field'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.810132713Z [INFO ] potentially running migration '20212212-total_summary_heartbeats'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.810282783Z [INFO ] no need to migrate '20212212-total_summary_heartbeats'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.810363338Z [INFO ] potentially running migration '20220317-align_num_heartbeats'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.810502975Z [INFO ] no need to migrate '20220317-align_num_heartbeats'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.810578747Z [INFO ] potentially running migration '20220318-mysql_timestamp_precision'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.810721077Z [INFO ] no need to migrate '20220318-mysql_timestamp_precision'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.81079248Z [INFO ] potentially running migration '202203191-drop_diagnostics_user'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.810937691Z [INFO ] no need to migrate '202203191-drop_diagnostics_user'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.811025183Z [INFO ] potentially running migration '20221016-drop_rank_column'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.811170988Z [INFO ] no need to migrate '20221016-drop_rank_column'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.81124974Z [INFO ] potentially running migration '20230219-add_astro_language'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.811391188Z [INFO ] no need to migrate '20230219-add_astro_language'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.811529028Z [INFO ] potentially running migration '20230219-add_subscription_renewal'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.81168032Z [INFO ] no need to migrate '20230219-add_subscription_renewal'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.811757318Z [INFO ] potentially running migration '20231023-fill_last_branch'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.811899685Z [INFO ] no need to migrate '20231023-fill_last_branch'
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.813408266Z [INFO ] creating job queue 'wakapi.default' (1 workers)
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.813537412Z [INFO ] creating job queue 'wakapi.processing' (1 workers)
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.813648328Z [INFO ] creating job queue 'wakapi.reports' (1 workers)
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.813718658Z [INFO ] creating job queue 'wakapi.housekeeping' (1 workers)
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.813804306Z [INFO ] creating job queue 'wakapi.mail' (1 workers)
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.814018565Z [INFO ] creating job queue 'wakapi.imports' (1 workers)
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.814088283Z [INFO ] scheduling report generation
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.814169848Z [INFO ] scheduling summary aggregation
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.814212828Z [INFO ] scheduling inactive users cleanup
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.815166512Z [INFO ] scheduling project stats cache pre-warming
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.815206486Z [INFO ] scheduling total time counting
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.815232136Z [INFO ] scheduling first data computing
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.817157959Z [INFO ] computing users' first data
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.817275989Z [INFO ] scheduling leaderboard generation
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.821486823Z [INFO ] 👉 Listening for HTTPS on 0.0.0.0:3080... ✅
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.821608589Z [INFO ] 👉 Listening for HTTPS on [::1]:3080... ✅
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: 2024-06-19T00:34:13.823527563Z [ERROR] listen tcp [::1]:3080: bind: address already in use
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: panic: listen tcp [::1]:3080: bind: address already in use
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: goroutine 57 [running]:
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: github.com/emvi/logbuch.(*StandardFormatter).Pnc(0x25423c0?, {0xc000ed86c0?, 0xc000ed86c0?}, {0x0?, 0x0?, 0x0?})
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]:         /home/ec2-user/go/pkg/mod/github.com/emvi/[email protected]/standard_formatter.go:57 +0x37
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: github.com/emvi/logbuch.(*Logger).Fatal(0x25423c0, {0xc000ed86c0, 0x33}, {0x0, 0x0, 0x0})
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]:         /home/ec2-user/go/pkg/mod/github.com/emvi/[email protected]/logger.go:132 +0x72
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: github.com/emvi/logbuch.Fatal(...)
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]:         /home/ec2-user/go/pkg/mod/github.com/emvi/[email protected]/funcs.go:55
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: main.listen.func2()
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]:         /home/ec2-user/go/pkg/mod/github.com/muety/[email protected]/main.go:394 +0x6a
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]: created by main.listen in goroutine 1
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal wakapi[3765]:         /home/ec2-user/go/pkg/mod/github.com/muety/[email protected]/main.go:392 +0x5e5
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal systemd[1]: wakapi.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun 19 00:34:13 ip-172-31-44-5.ap-south-1.compute.internal systemd[1]: wakapi.service: Failed with result 'exit-code'.

i have not yet been able to access the website from any public url , while on port forwarding i can see that it works when the listen_ipv4 is set to localhost in the config.yml.

[muety]

If you set the listen IP to localhost, you'll also only be able to access it from localhost. Set it to 0.0.0.0 (or the specific IP of your public network interface) to expose it publicly instead. Also the bind: address already in use suggests that the IPv6 port 3080 is already blocked. Perhaps you have another Wakapi instance already running on that port? You can check with netstat -tulpn | grep 3080.

[YC]

Is there any way to verify the page is being served using CURL on the ec2 instance?

$ curl http://localhost:3000

I wouldn't recommend exposing a service over the Internet over http though.
You should use https or set up a reverse proxy with caddy/nginx/haproxy etc. to serve multiple apps over 80/443 (which you presumably allowed in the security group).

[palash-sarate]

Is there any way to verify the page is being served using CURL on the ec2 instance?

$ curl http://localhost:3000

I wouldn't recommend exposing a service over the Internet over http though. You should use https or set up a reverse proxy with caddy/nginx/haproxy etc. to serve multiple apps over 80/443 (which you presumably allowed in the security group).

as application is running fine on local host it return the landing page correctly. the dns to public url resolves correctly but when trying to curl the public URL connection fails

[ec2-user@ip-172-31-44-5 ~]$ curl https://wakatime.zeuron.ai
curl: (7) Failed to connect to wakatime.zeuron.ai port 443 after 55 ms: Couldn't connect to server

I am now trying to setup nginx as reverse proxy that also handle ssl termination , as this did not work.

[muety]

If you're hosting nothing but Wakapi on the server, setting up a reverse proxy is probably overkill tbh. You can have Wakapi serve via TLS itself using the server.tls_* config variables. Also, for initial testing, you can also just go with plain HTTP as long as you switch to HTTPS in the long run.

Also, again, if Wakapi is listening on 3000, you'll need a firewall rule to allow incoming traffic to that port and then access https://wakatime.zeuron.ai:3000.

[palash-sarate]

If you're hosting nothing but Wakapi on the server, setting up a reverse proxy is probably overkill tbh. You can have Wakapi serve via TLS itself using the server.tls_* config variables. Also, for initial testing, you can also just go with plain HTTP as long as you switch to HTTPS in the long run.

Also, again, if Wakapi is listening on 3000, you'll need a firewall rule to allow incoming traffic to that port and then access https://wakatime.zeuron.ai:3000.

I think this would work, is there any way to avoid any port number. I tried setting it to 443, 80 but got permission denied.

[muety]

The CapabilityBoundingSet=CAP_NET_BIND_SERVICE setting in the service file should account for that. Perhaps google for "linux allow bind privileged ports".

[palash-sarate]

Hi, I am trying to use helm chart now on my eks cluster. but I am getting an error in pod logs

2024-06-19T15:15:37.309231072Z [ERROR] unexpected end of JSON input
panic: unexpected end of JSON input
goroutine 1 [running]:
github.com/emvi/logbuch.(*StandardFormatter).Pnc(0x2520100?, {0x11d5162?, 0x11d5162?}, {0x0?, 0x0?, 0x0?})
/go/pkg/mod/github.com/emvi/[email protected]/standard_formatter.go:57 +0x37
github.com/emvi/logbuch.(*Logger).Fatal(0x2520100, {0x11d5162, 0x1c}, {0x0, 0x0, 0x0})
/go/pkg/mod/github.com/emvi/[email protected]/logger.go:132 +0x72
github.com/emvi/logbuch.Fatal(...)
/go/pkg/mod/github.com/emvi/[email protected]/funcs.go:55
github.com/muety/wakapi/config.readColors()
/src/config/config.go:426 +0x145
github.com/muety/wakapi/config.Load({0x11c09f5, 0xa}, {0x11bcc34, 0x7})
/src/config/config.go:469 +0x2ad
main.main()
/src/main.go:122 +0x138

I have used the helm chart from suggested repo as is since i didnt see any need to change anything except smtp settings, and simply used helm to install.

I will create a guide to host on eks or ec2 if I succeed in either.