starred/go-librespot

Fork 0

mirror of https://github.com/devgianlu/go-librespot.git synced 2026-04-26 05:15:49 +03:00

[GH-ISSUE #119] CORS issues still present? #73

New issue

Closed

opened 2026-02-28 14:25:08 +03:00 by kerem · 5 comments

kerem commented

2026-02-28 14:25:08 +03:00

Owner

Originally created by @thilojaeggi on GitHub (Oct 6, 2024).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/119

So I just cloned the latest version and tried to connect to the websocket in my flutter app but keep getting a connection refused error.
This is my config:

device_name: nordan
log_level: debug
credentials:
  type: zeroconf
device_type: speaker
server:
  enabled: true
  address: ""
  port: 3678
  allow_origin: "*"

Originally created by @thilojaeggi on GitHub (Oct 6, 2024). Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/119 So I just cloned the latest version and tried to connect to the websocket in my flutter app but keep getting a connection refused error. This is my config: ``` device_name: nordan log_level: debug credentials: type: zeroconf device_type: speaker server: enabled: true address: "" port: 3678 allow_origin: "*" ```

kerem closed this issue

2026-02-28 14:25:09 +03:00

kerem commented

2026-02-28 14:25:09 +03:00

Author

Owner

@thilojaeggi commented on GitHub (Oct 6, 2024):

Weird, with the pre built binary for v0.0.17.1 it works?

@thilojaeggi commented on GitHub (Oct 6, 2024): Weird, with the pre built binary for [v0.0.17.1](https://github.com/devgianlu/go-librespot/releases/tag/v0.0.17.1) it works?

kerem commented

2026-02-28 14:25:09 +03:00

Author

Owner

@aykevl commented on GitHub (Oct 7, 2024):

What does your log say?
It should say something like the following:

INFO[0000] api server listening on [::]:3678

Also, "connection refused" is probably not a CORS issue.

@aykevl commented on GitHub (Oct 7, 2024): What does your log say? It should say something like the following: ``` INFO[0000] api server listening on [::]:3678 ``` Also, "connection refused" is probably not a CORS issue.

kerem commented

2026-02-28 14:25:09 +03:00

Author

Owner

@devgianlu commented on GitHub (Oct 12, 2024):

@thilojaeggi Please check that the configuration file is being read properly, you can find how to migrate in #103:

The simplest option to keep the previous behavior is by using --config_dir=.. This will keep reading the configuration from the current working directory, and stores the app state there.
To move the configuration to the new location, use:
$ mkdir ~/.config/go-librespot
$ mv credentials.json config.yml ~/.config/go-librespot/

@aykevl I think the README should be updated detailing how the configuration works after #103.

@devgianlu commented on GitHub (Oct 12, 2024): @thilojaeggi Please check that the configuration file is being read properly, you can find how to migrate in #103: > The simplest option to keep the previous behavior is by using `--config_dir=.`. This will keep reading the configuration from the current working directory, and stores the app state there. To move the configuration to the new location, use: > ``` > $ mkdir ~/.config/go-librespot > $ mv credentials.json config.yml ~/.config/go-librespot/ > ``` @aykevl I think the README should be updated detailing how the configuration works after #103.

kerem commented

2026-02-28 14:25:09 +03:00

Author

Owner

@devgianlu commented on GitHub (Oct 20, 2024):

@thilojaeggi I have updateded the README to have a more detailed explaination on how the configuration works.

I'll be closing this as connection refused is most definitely not a CORS issue. Feel free to open another issue if needed.

@devgianlu commented on GitHub (Oct 20, 2024): @thilojaeggi I have updateded the README to have a more detailed explaination on how the configuration works. I'll be closing this as `connection refused` is most definitely not a CORS issue. Feel free to open another issue if needed.

kerem commented

2026-02-28 14:25:10 +03:00

Author

Owner

@aykevl commented on GitHub (Oct 21, 2024):

@aykevl I think the README should be updated detailing how the configuration works after #103.

Oops, sorry I missed the other server: configuration in the README! Thanks for fixing!

@aykevl commented on GitHub (Oct 21, 2024): > @aykevl I think the README should be updated detailing how the configuration works after #103. Oops, sorry I missed the other `server:` configuration in the README! Thanks for fixing!