| 3 Jul 2020 |
 scar45 | I have changed FUNKWHALE_HOSTNAME in my .env file, but again, all songs/users/libraries are still associated with that original domain that I used when setting FW up initially | 19:38:25 |
| scar45 | any help would be greatly appreciated, thanks in advance! | 19:38:40 |
| scar45 | * I have changed FUNKWHALE_HOSTNAME in my .env file, but again, all songs/users/libraries are still associated with that original domain that I used when setting FW up initially | 19:38:51 |
| scar45 | (I also tried modifying the original domain via Django -> Home › Federation › Domains, but it just created a new domain instead of modifying the old one, probably by design, which doesn't help me much) | 19:40:01 |
| scar45 | Ooop, I just found this, and I think it may help!
https://docs.funkwhale.audio/admin/url.html
| 19:43:00 |
| scar45 | Alright that appeared to work somewhat, but it seems that the Users still belong to the original domain, and in Django, that original domain is the only one there, since I deleted the new/empty one I noted above | 19:55:21 |
| scar45 | * Alright that appeared to work somewhat, but it seems that the Users still belong to the original domain, and in Django, that original domain is the only one there, since I deleted the new/empty one I noted above | 20:07:16 |
| scar45 | This was the only issue from the log I noted:
- 0/8 federation.Actor.url
Replacing url on 0 federation.Actor…
...all other N/N references were updated successfully, but this one, which is probably why I am seeing those users associated to the old domain
| 20:08:38 |
| scar45 | Alright I've just edited each of those 8 manually via Django -> Federation -> Accounts, and everything is looking great now. Apologies for this wall of text! | 20:19:01 |
|  MSavoritias joined the room. | 22:15:59 |
| 4 Jul 2020 |
 nathan67_ | Hello !
I have a problem with the REST API when I try to access the listen URL, for example:
"listen_url": "/api/v1/listen/450cb724-7a97-449d-a6e1-80b88811ba0c/"
I do a GET request on https://my_website.xx/api/v1/listen/450cb724-7a97-449d-a6e1-80b88811ba0c/
But it give me a 404 error and this in the docker logs :
2020-07-04 16:09:22,294 django.request WARNING Not Found: /api/v1/listen/450cb724-7a97-449d-a6e1-80b88811ba0c/
But if I try the same URL later it works. | 16:15:01 |
 Agate (she/her) | How did you get the UUID you are using in the URL ? | 17:31:50 |
| Agate (she/her) | (it should be a track uuid, not an upload uuid) | 17:32:08 |
| 5 Jul 2020 |
 hdasch |
I've just ugraded to 0.21.1 running with docker-compose. I can browse and listen to music through the web interface. When I access the server with DSub, it fails with "A problem occurred communicating with your server. The nginx front end reports "404 for POST /rest/getAlbumList.view?u=c...". docker-compose logs -f --tail=50 api" reports "django.request WARNING Not Found: /api/subsonic/rest/getAlbumList.view". Is this a DSub issue or a server issue? | 05:28:17 |
| hdasch | Never mind. Found the API keys. Have no idea why this worked before. But the Subsonic specific password works. | 05:46:43 |
| nathan67_ | In reply to @Eliot:matrix.org
How did you get the UUID you are using in the URL ? Via the API, here for example: | 09:29:55 |
| nathan67_ | 
Download image.png | 09:29:59 |
| Agate (she/her) | okay, are you authenticated when you make the request? | 09:38:24 |
| Agate (she/her) | if the upload is in a private library, this isn't likely to work | 09:38:34 |
| 6 Jul 2020 |
| nathan67_ | Yes I am authenticated and it's in a public library (the API is also available for non-registered users)
But it's an error because I get 404 and the log give an error as above. | 06:02:52 |
| Agate (she/her) | The track is probably not in a public library : https://zik.bretzel.ga/library/tracks/1160 | 06:39:17 |
| Agate (she/her) | It's not marked as playable and there is no "related library" on the track page | 06:39:49 |
| nathan67_ | If I am connected I can see it | 09:02:56 |
| nathan67_ | Is there any way to put it all out in public? (I am the owner of the instance so I can edit everything if necessary) | 09:04:23 |
| nathan67_ | I mean that everyone could listen to the music without having an account, which would also solve my problem. | 09:08:00 |
 sporiff (he/him) | You should be able to change the visibility of libraries to public if you are the instance owner (administration > Library > Libraries > Select library > change "Visibility"). If you wanted to make it so that an account was not needed to listen to music at all, you would need to uncheck the "API requires authentication" option in the instance settings | 09:23:41 |
| Agate (she/her) | In reply to @nathan67_:matrix.org
Is there any way to put it all out in public? (I am the owner of the instance so I can edit everything if necessary) if you can see it when connected, it's probablà because its visibility is "Instance only", instead of "public" | 10:53:23 |
| nathan67_ | In reply to @sporiff:garappa.chat
You should be able to change the visibility of libraries to public if you are the instance owner (administration > Library > Libraries > Select library > change "Visibility"). If you wanted to make it so that an account was not needed to listen to music at all, you would need to uncheck the "API requires authentication" option in the instance settings Okay this worked! Now I don't have any problem with 404 or things like that thanks | 10:54:52 |
| nathan67_ | If you want to try what I made : https://bretzel.ga/musique/ | 10:55:52 |
|  futurecat joined the room. | 12:03:32 |
