starred/godoxy
1
0
Fork 0
mirror of https://github.com/yusing/godoxy.git synced 2026-01-14 06:13:33 +01:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

Backend fails to start #36

New Issue
Closed
opened 2025-12-29 09:21:52 +01:00 by adam · 7 comments
adam commented 2025-12-29 09:21:52 +01:00
Owner
Copy Link

Originally created by @erkkimadisson on GitHub (Feb 6, 2025).

So when ever its trying to start the backend of go-proxy its giving me the following error

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xb64d1a]
goroutine 86 [running]:
github.com/yusing/go-proxy/internal/notif.Notify(0xc0003306c0)
	/src/internal/notif/dispatcher.go:46 +0x1a
github.com/yusing/go-proxy/internal/watcher/health/monitor.(*monitor).checkUpdateHealth(0xc000145180)
	/src/internal/watcher/health/monitor/monitor.go:224 +0xbe6
github.com/yusing/go-proxy/internal/watcher/health/monitor.(*monitor).Start.func1()
	/src/internal/watcher/health/monitor/monitor.go:86 +0x2d5
created by github.com/yusing/go-proxy/internal/watcher/health/monitor.(*monitor).Start in goroutine 1
	/src/internal/watcher/health/monitor/monitor.go:73 +0x20e

Never had issues like this when using docker or any other app so i have no idea what to do.

Originally created by @erkkimadisson on GitHub (Feb 6, 2025). So when ever its trying to start the backend of go-proxy its giving me the following error ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xb64d1a] goroutine 86 [running]: github.com/yusing/go-proxy/internal/notif.Notify(0xc0003306c0) /src/internal/notif/dispatcher.go:46 +0x1a github.com/yusing/go-proxy/internal/watcher/health/monitor.(*monitor).checkUpdateHealth(0xc000145180) /src/internal/watcher/health/monitor/monitor.go:224 +0xbe6 github.com/yusing/go-proxy/internal/watcher/health/monitor.(*monitor).Start.func1() /src/internal/watcher/health/monitor/monitor.go:86 +0x2d5 created by github.com/yusing/go-proxy/internal/watcher/health/monitor.(*monitor).Start in goroutine 1 /src/internal/watcher/health/monitor/monitor.go:73 +0x20e ``` Never had issues like this when using docker or any other app so i have no idea what to do.
adam closed this issue 2025-12-29 09:21:52 +01:00
adam commented 2025-12-29 09:21:53 +01:00
Author
Owner
Copy Link

@garrettstoupe commented on GitHub (Feb 6, 2025):

this is happening to me as well

@garrettstoupe commented on GitHub (Feb 6, 2025): this is happening to me as well
adam commented 2025-12-29 09:21:53 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Feb 6, 2025):

could u send me the content of config.yml under providers.notification? (with sensitive info redacted)

@yusing commented on GitHub (Feb 6, 2025): could u send me the content of `config.yml` under `providers.notification`? (with sensitive info redacted)
adam commented 2025-12-29 09:21:53 +01:00
Author
Owner
Copy Link

@erkkimadisson commented on GitHub (Feb 6, 2025):

i just set it up using the backend version of 0.9.3 and frontend 0.9.2 and it is working now

could u send me the content of config.yml under providers.notification? (with sensitive info redacted)

It is the default i haven't yet modified anything from it as i am still testing it overall

@erkkimadisson commented on GitHub (Feb 6, 2025): i just set it up using the backend version of 0.9.3 and frontend 0.9.2 and it is working now > could u send me the content of config.yml under providers.notification? (with sensitive info redacted) It is the default i haven't yet modified anything from it as i am still testing it overall
adam commented 2025-12-29 09:21:53 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Feb 6, 2025):

Fixed, pls wait for GitHub to build

@yusing commented on GitHub (Feb 6, 2025): Fixed, pls wait for [GitHub to build](https://github.com/yusing/go-proxy/actions/runs/13186080480)
adam commented 2025-12-29 09:21:54 +01:00
Author
Owner
Copy Link

@erkkimadisson commented on GitHub (Feb 6, 2025):

Amazing to hear that devs are this active :D
Keep up the good work

@erkkimadisson commented on GitHub (Feb 6, 2025): Amazing to hear that devs are this active :D Keep up the good work
adam commented 2025-12-29 09:21:54 +01:00
Author
Owner
Copy Link

@yusing commented on GitHub (Feb 6, 2025):

@erkkimadisson @garrettstoupe Done, pls pull the image again. Hope u guys love this project.

@yusing commented on GitHub (Feb 6, 2025): @erkkimadisson @garrettstoupe Done, pls pull the image again. Hope u guys love this project.
adam commented 2025-12-29 09:21:54 +01:00
Author
Owner
Copy Link

@erkkimadisson commented on GitHub (Feb 6, 2025):

Alright now it is working 👍

@erkkimadisson commented on GitHub (Feb 6, 2025): Alright now it is working 👍
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
 wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy#36
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?