00:03:43 How can I set rec src on a device? 00:03:56 for some reason my mic is set to playback 00:04:08 and it is a different device to sound out 00:04:58 things be funky 00:38:50 need rdp (xrdp, xorg, bhye) help https://termbin.com/p83f 00:53:49 Re https://bsd.to/VxmW -- looks like mortal user did not initialize the root's environment, much what rwp wrote about the leakage 00:53:50 Title: dpaste/VxmW (Plain Text) 01:11:24 * skered polls for any misc/nut users... Does nut (nutmon) respect deadtime? I get the felling it's something with usbhid-ups that seems to restart/flicker USB. 01:17:15 ... re fish history, also looks like HOME was either set to "/", or was just unset, after being root 01:50:49 meena: i'm not allowed to run my own mail 02:05:37 skered, what were you looking at in nut_upsmon? 02:11:11 s2r: Just trying to understand cases of upsd going down and why upsmon wants to shutdown. 02:12:39 Which I can trigger by restarting upsd. 02:14:58 skered, But does it shutdown the server? I don't think upsmon kills anything if it losses connectivity 02:15:44 skered it shutsdown when the battery levels reach predetermined low values. 02:15:45 I think it's MINSUPPLIES that's causing it. 02:16:08 But what are you observing? 02:16:19 restart upsd, shutdown starts. 02:19:09 skered wow. 02:20:09 I had many issues with my upss fortunarely detected disconnections to the ups but never initiated the shutdown. 02:21:33 can you paste your upsmon.conf ? 02:23:02 have you tried with upsmon -DDD to debug? 02:23:15 The difference here is upsmon talking to upsd not disconnection to the UPS. 02:27:47 I know that removing power from the UPS works and keep everything up. 02:27:53 I have an idea what was going during my tests. 02:28:19 I don't think the state was saved correctly or I restarted upsd during a calibartion. 02:29:02 Or it's not changing the state when I run a test via test.battery.start.quick or test.battery.start.deep. 02:36:22 https://gist.github.com/derekschrock/047175203cf44a4a31f510ce59dbc93b 02:36:24 Title: gist:047175203cf44a4a31f510ce59dbc93b · GitHub 02:36:28 But that's uspmon.conf 02:42:52 skered check mine. https://bsd.to/MT8f less options 02:42:53 Title: dpaste/MT8f (Plain Text) 02:43:22 No deadtime, no minsupplies 02:43:42 It should be defaulting to 30. I don't know aout minsupplies. 02:44:39 er well maybe 15. I thought I saw 30 in source. 02:45:00 And MINSUPPLIES should be defaulting to 1. 02:45:37 But I take it if you restart upsd while upsmon is running it doesn't trigger a shutdown? 02:49:18 s2r: How are you connected too? USB? serial? 02:49:35 skered, I've got to UPSs sonnected via USB 02:50:10 skered I'm 95% sure I tried it and it doesn't shutdown. 02:50:40 Don't want to try at 23:50 here before a working day. 02:50:42 :) 02:54:14 People work the last week of the year? Like yuck. 03:00:09 need rdp (xrdp, xorg, bhye) help https://termbin.com/p83f 03:24:15 why is usbhidaction not doing anything for me? 03:25:29 https://forums.freebsd.org/threads/howto-using-multimedia-keys-from-uhid-4-devices.24069/ 03:25:31 Title: HOWTO: Using multimedia keys from uhid(4) devices | The FreeBSD Forums 03:25:36 I am TRYING to follow that ^^^ 03:30:17 OK, let's take it step by step. What does the grep in step 1 show you? 03:35:11 polyex: Is i3 in your PATH? 03:35:27 o/ 03:35:45 or bash even? 03:36:17 Change that shabang to not use /usr/bin/env. 03:40:44 s2r: You know what I'm sure it's was that I run a deep test and forgot about it looking back on upslog logs. 03:41:41 It seems that upsmon doesn't send an even for a deep test. 03:42:18 vs quick where you see the USB flip and and admin off/sleep (and maybe a CAL) then not admin off/sleep. 03:44:39 V_PauAmma_V, it shows me that it is likely Apple keyboard on uhid1 03:45:00 and step 2 confirms it is indeed uhid1 03:45:18 because it hows up page=Comsumer usage=Play/pause etc. 03:50:12 OK. What do you have in the action file you created at step 3? 03:57:54 polyex: "UserWindowManager=.config/xrdp/startwm.sh", you likely want absolute path here? using $HOME or whatever is allowed in that .ini file 03:59:20 V_PauAmma_V, $ cat usbaction.conf 03:59:20 Consumer:Volume_Increment 1 0 mixer -f $1 vol +$2 03:59:20 Consumer:Mute 1 0 mixer -f $1 mute 04:01:31 And both keys show up in step 2? 04:03:43 yes and more, here are some 04:03:47 Input rid=0 pos=6 size=1 count=1 page=Consumer usage=Volume_Increment, logical range 0..1 04:03:53 Input rid=0 pos=4 size=1 count=1 page=Consumer usage=Mute, logical range 0..1 04:05:52 OK. So far so good. Now at step 4, what command do you enter? 04:06:07 yuripv: It should be relative ot the user logging in home dir 04:07:16 # usbhidaction -d -f /dev/uhid1 -c usbaction.conf /dev/mixer3 2 04:07:16 ^[[24~^[[24~^[[21~^[[21~^[[21~ 04:07:36 the funny input is me trying the MM keys, but getting 24's and 21's 04:07:42 gibberish 04:08:39 the keys are still operating as F8 and F12, instead of mute and volume increment, respectively 04:08:58 even though I am holding down the fn (function key) which is meant to activate them 04:11:06 Just in case that's the problem, try giving the full path to your usbaction.conf file. 04:11:21 it is in the pwd, but ok 04:14:50 no diff 04:18:38 Hmm. "^[[24~^[[24~^[[21~^[[21~^[[21~" smells to me like your fn key is not doing what it should do. 04:18:54 yeah 04:19:14 I do not know what to do, I mean, it works ok in Linux so it should not be a fault of the keyboard 04:28:35 but yes, the fn key 04:28:49 it's an apple A 1243 04:28:51 fwiw 04:29:58 What happens if you *don't* press the fn key? 04:30:35 same as if I do 04:30:53 it just acts as a F10 key or F12 key etc. 04:31:01 and if I do use fn key, same 04:31:47 AumShivaya: is it a thinkpad? 04:32:15 no a desktop 04:32:19 with a usb wired keyboard 04:37:06 so no 'fn lock' key 04:37:23 nope 04:38:25 I'm wondering: is the fn key handled in keyboard firmware as a state change key, or is it passed to the computer as a keypress? 04:39:08 my prototype is working again :3 04:40:07 I do not know 04:40:08 but 04:40:18 xev does not register it if I press the fn key 04:43:02 Is that xev under FreeBSD, or under Linux? 04:46:25 need rdp (xrdp, xorg, bhye) help pls https://termbin.com/p83f 04:52:27 freebsd 04:52:36 should I check with linux and see? 04:52:43 It would require a reboot a bit later 04:54:31 I have the feeling it is passed as a keypress in linux, but I would have to check :/ 04:57:48 I was thinking along those lines too. But no need to run to check. I'm about to go to bed. 05:05:11 polyex, If you don't an answer, try freebsd-questions@ mailing list (https://lists.freebsd.org/subscription/freebsd-questions ) 05:05:12 Title: FreeBSD Mailing lists: subscription for freebsd-questions 05:05:41 ty 05:06:26 s/If you don't an answer/If you don't get an answer/ # fudge 05:06:56 polyex: You might want to look at scrollback? 05:07:17 skered ok 05:08:33 yuripv man page for sesman.ini states "Path of the startup script relative to the user's home directory." 05:08:47 so no absolute not needed 05:08:56 polyex: Go back some more. 05:09:47 i3 in my PATH hmm... 05:09:58 And bash? 05:10:07 Just use /bin/sh 05:10:16 And try again 05:10:30 To see if the init. touch is executing. 05:10:53 PATH has /usr/local/bin in it and which i3 says /usr/local/bin/i3 so ya it must be in PATH 05:11:10 just use /bin/sh? 05:11:11 How are you checking that? 05:11:29 what? 05:11:31 Your PATH might be different at the time of executing that script 05:11:36 hmm 05:12:02 in my ~/.login_conf i have setenv which should build up the env there. any way to test? 05:12:19 lemme add the sesman.log output when i try to connect to the example code 05:12:25 Change the shabang of the script to use /bin/sh 05:12:40 of startwm.sh? 05:12:43 Yeah 05:12:46 k sec 05:18:49 didn't work 05:19:41 Ok I think you need to get the debug logs of sesman up then 05:20:05 almost gottem, sec 05:23:25 Are you sure you're using Xorg session type too? 05:23:53 https://termbin.com/cv8iw 05:23:59 no 05:24:09 what is that and what should it be? 05:24:43 You have xauth installed? 05:25:03 it seems to be when i type which xauth 05:26:47 Is your user in the video group? 05:27:06 no, only polyex, wheel, and operator 05:27:24 which works just fine in my other bhyve that's working. i'll double check that rn tho 05:28:14 You have debug logs turned on in that sesman.ini? 05:28:36 ok ya no video group for other guest 05:28:43 dunno... 05:29:22 no just info 05:29:25 i'll change to debug rn 05:31:13 Is xrdp-chansrv running after Xorg? 05:31:31 Xorg, chansrv, userwm. 05:31:35 Should be the order of things 05:34:28 ok... 05:35:14 And you have xorgxrdp installed too? 05:37:28 ~/..xorgxrdp....log and ~/.xsession-erros might help as wlel 05:37:40 .xorgxrdp....log 05:39:27 xorgxrdp is installed ya. no log at /var/log/xorgxrdp.log 05:39:33 https://termbin.com/a3wf 05:39:44 that has xrdp-sesman.log for DEBUG level 05:40:00 problem starting X i guess? 05:40:16 but Xorg shows up in the top for polyex when i'm connecting 05:41:38 And your touch isn't creating the file? 05:41:40 ok and nothing matching "chan" shows up in top when connecting 05:41:43 nope 05:42:14 Is this slow/old hardware? 05:42:29 The two vms are speced the same? 05:42:32 no it's a bhyve guest vm running on nice gear 05:42:34 on the same host 05:42:36 ya 05:42:38 ok 05:42:45 same 13.2 everywhere 05:43:25 You don't have a xorg log in your home dir? 05:43:37 .xorgxrdp.10.log 05:44:56 nope 05:45:07 .xsession-error? 05:45:30 What about 05:45:30 there's .local/share/xrdp/xrdp-chansrv.10.log but 0 size 05:45:31 ~/.local/share/xrdp 05:45:40 nothing else in it 05:46:01 no .xsession-error 05:46:56 /var/log/Xorg.anything? 05:47:17 nope 05:50:56 Can you write to /tmp? 05:51:15 and if this isn't an example of why configuration management is worthwhile, i don't know what is 05:51:30 can i write to tmp as my user or? 05:51:49 as the user that's logging to into xrdp 05:52:01 Check for all those .X11 dirs. 05:52:49 /tmp/.X11-unix/X10 is what Xorg should be creatign 05:53:05 OMG 05:53:30 dude /tmp is like 755 not 777 05:54:24 ok, so I booted in to linux, and back...and it does not seem to treat the fn key (xev utility) as a keypress 05:54:28 aaand, that was it 05:54:42 V_PauAmma_V, 05:54:43 skered, tyvm my bro 05:55:06 also I am getting this error for Xorg: > Warning: Key not found in evdev+aliases(qwerty) keycodes 05:55:06 > Not treating as an overlay key 07:07:34 is it ok if paths in my ~/.login_conf have ~ in them? or should they be absolute? 07:08:41 I would use "$HOME" instead of "~". And set HOME once to the directory 07:08:55 ... before any use 07:09:23 set HOME where tho? 07:10:11 Whatever use home directory happens to be ... I don't know , /home/polyex 🤷🏽‍♂️ 07:10:21 s/use/&r/ 07:11:10 sorry i still don't get it. in .login_conf i use $HOME instead of /home/polyex but i still don't understand where i'm supposed to set HOME 07:11:19 "once to the directory" 07:12:05 Context is same as when you started for setting HOME variable: is it ok if paths in my ~/.login_conf have ~ in them? or should they be absolute? 07:12:26 ... that is in "~/.login_conf" 07:12:52 i set HOME in .login_conf, like above the me:\ line? 07:17:21 or :HOME=/home/polyex:\ in the me:\ block, before :setenv line? 07:17:55 My purpose of setting HOME, instead of relying on it being set after login, to avoid tedious work of chasing down things not working when using configuration files across multiple software on FreeBSD & CentOS-derivatives 07:18:35 ya ok so you're saying, set HOME right at the core, in ~/.login_conf, then use it safely everywhere else? 07:18:49 polyex, Sorry, ignore me please regarding "~/login_conf"; have not relied or knowingly used it 07:19:08 s,/,&., 07:19:16 where does HOME get set by on freebsd? 07:20:42 well, one location is the /etc/*passed file 07:21:03 "/etc/*.passwd" that is 07:25:14 * parv does not have a "~/.login_conf", unsurprisingly 07:33:18 polyex: $HOME is set by whatever logs the user in, usually login(1), su(1) or sshd(8) 07:38:26 V_PauAmma_V: it does seem like a timing issue, but i just rebooted a few times (for unrelated reasons) and the problem hasn't come back. i noticed my userland was slightly out of date compared to the kernel (1400502 vs 1400501), perhaps that was the reason 09:27:06 unixwitch ok so it should be pretty reliable whether interactive login or service login then as long as env is invoked for the user. so then what format do you use for paths in ~/.login_conf? absolute /home/unixwitch/foo/bar, $HOME/foo/bar, or? 09:28:24 polyex: i don't have a .login_conf, but if i did, i'd probably use ~/foo/bar following the example in /etc/login.conf 09:29:22 login.conf(5) says this works for "capabilities that set environment variables" which is probably the only place you'd want to use it anyway 09:31:02 specifically only :setenv entries, or :path too? 09:31:22 it must be both, because the default class uses it in :path= 09:31:39 true 09:31:49 alright, done deal. tyvm 09:31:54 well, i haven't tested it with setenv, so perhaps it only works for path, but that would contradict the manpage 09:33:16 UNIX Witches get magic from daemons 09:34:15 what's a witch? 09:34:35 so switching from python 3.9 to 3.10 requires recompiling devel/electron25, time to find something else to do for four hours... 09:43:58 just four? 09:45:31 * meena is mildly jealous of whatever hardware unixwitch has at their disposal 09:47:59 meena: i think it took about 3:30 last time. no special hardware, Ryzen 7 5800X3D 09:52:59 i only have it installed for signal-desktop, hopefully one of the native IM clients might add signal support at some point 09:57:31 unixwitch: it's very frowned upon by the signal developers. not quite as much as by discord, but still 09:59:33 i'm mildly impressed that this is causing no issues at all with audio playback in firefox: 9:59AM up 2:42, 3 users, load averages: 24.66, 20.58, 15.06 09:59:53 used to be (years ago) doing anything at all on the cpu would make anything latency-sensitive very sad 10:04:07 ya that's really impressive 10:04:10 why load so high? 10:04:18 24.66 never even seen that 10:05:09 polyex: unixwitch is building electron 10:05:40 and smooth audio playback that's some nice scheduler upgrades? 10:06:01 polyex: poudriere... in this case i used 'poudriere bulk -J8' which runs 8 jobs in parallel, but sometimes it ends up building a few packages which i've set ALLOW_MAKE_JOBS_PACKAGES for, which means each of those gets 8 jobs by itself, so you end up with a lot of jobs 10:06:44 it's not really ideal because running that many compilers in parallel is not efficient, but it's quicker than not using -J at all, and sadly setting ALLOW_MAKE_JOBS still breaks some packages 10:07:57 polyex: not sure exactly why it works, but i'm using the new(ish) mac_priority(4) which allows jackd to run with realtime priority. so it's firefox > pulseaudio > jackd > snd_uaudio, i guess pulseaudio has a fairly large buffer, and jackd's realtime priority means it's okay with its smaller buffer 10:08:38 damn that's so cool 10:08:56 how do you apply the mac priority policy to jackd? 10:09:27 load mac_priority (either as a module, or compile it into the kernel), put yourself in the realtime group (gid 47) and then start jackd with -R 10:09:37 jackd_args="-R -doss -r48000 -p671 -n2 -w24 -e -P /dev/dsp0.0 -C /dev/dsp0.1" 10:10:26 it seems to get a bit confused by my 20-channel snd_uaudio device, the default -p1024 prints a warning saying to use a multiple of 671, but any value other than 671 causes it not to start at all... which seems like a bug but i haven't gotten around to investigating it yet 10:14:40 polyex: if you're interested in jackd on freebsd, i found this page very helpful: https://github.com/0EVSG/freebsd_jack_notes 10:14:41 Title: GitHub - 0EVSG/freebsd_jack_notes: Notes and user guides for jack audio server on FreeBSD 10:26:14 wow ty 10:27:48 unixwitch: how much Software do you have to recompile to work with Jack? 10:28:14 * meena puts on Mr Jack by System of a Down 10:29:53 meena: so far only pulseaudio, because the default options don't include the jack sink. then everything else uses PA. (that's obviously not good for serious audio work, but it's fine for desktop applications) 10:30:23 i'm intending to try ardour, which should use jack directly, but didn't have time yet 10:30:57 why would pulseaudio *not* include jack support out of the box? 10:31:55 i don't know. it adds a dependency on audio/jack but that's a pretty small package 10:34:45 given the amount of people who would benefit from this, it seems a small sacrifice to make to the freaks who are like, as little deps as possible 10:35:36 OTOH, most of those people might be recompiling everything to not use pulseaudio because it was once touched by Poettering 10:36:40 i noticed a few things (including firefox) also have native jack support, but i actually prefer to route that stuff through PA because it's a bit more configurable, like forcing it to use only channel 1 for capture instead of thinking i have a stereo mic input. unless you can configure that directly in jack, maybe i should look at the manual... 10:39:00 for jack-pulseaudio tunnelling (or jack-pipewire), jackdbus works better than jackd (both link to libjackserver) 10:40:24 recently jackd got libdbus dependency too, so it could work if jackd emits jack-server-started and jack-server-stopped signals over dbus, so that pulseaudio or pipewire can create the tunnel dynamically 10:41:01 oh, electron25 build finished in 50 minutes, thanks ccache! 10:42:09 i'm jackdbus and ladish upstream and i noticed that ladish (that requires jackdbus) got recently added to freebsd ports 10:42:47 i dont have freebsd installed, but the design is same for linux and freebsd 10:42:59 recently (in freebsd-15) 10:46:21 unixwitch: in jack it is up to the driver what hardware ports to present. whether mic or guitar is attached to the audio io port is not something jack knows 10:46:52 but (oss) drivers can present mono devices i guess 10:50:42 nedko: right. my concern is that i connect firefox directly to jack, and it sees a 20-channel capture device, it's not going to know what to do with that. using PA's jack sink with channels=1 forces all the clients to just use a mono input, which is what i want for desktop apps 10:56:48 unixwitch: i understand, thanks for the info. ladish has "rooms" concept to limit visibility of nodes, but proper support in jack is needed for restricting the view of a program to a virtual hw with ports linked to particular hardware 10:56:54 what ports category would you put a Python Chromecast library in (PyChromecast)? devel/ because it's a library, not an end-user application? 10:57:33 or net/ because it implements a network protocol 10:59:16 nedko: hmm... ladish is like a persistent version of qjackctl? 11:00:18 unixwitch: i think qjackctl can also persist connections, ladish aims to do it automagically 11:01:09 that sounds interesting, i might have a look 11:01:33 ladish requires no session management protocol for the basic functionality (restoring connections) 11:02:02 even when jack client name is random 11:05:35 unixwitch: in case you've not found it already: https://lists.freebsd.org/archives/dev-commits-ports-all/2023-December/092042.html 11:05:36 Title: git: d92825bc02a5 - main - audio/ladish: New port: Session management system for JACK 11:54:49 good morning 11:57:00 heya 11:57:00 i have an application that requires electron 19 package since upgrading to freebsd 14 that package is no longer avaiable only election 25 my question is is there a way to compile an older version of election on freebsd ? 12:23:47 bsdbandit: if it does compile, you can just grab the old stuff (Makefile, package source, etc.) and make a package with it 12:24:01 bsdbandit: you could perhaps check out an older version of the ports tree (like a quarterly release) that still includes it and build a package 12:25:16 it looks like the port was removed on Fri Jun 30 2023, so 2023Q2 for example should still have it 12:26:04 however, it was removed because it's EOL upstream, so it probably has unfixed security issues 12:28:56 welp i submitted my first port, let's find out how many things i did wrong 12:46:42 hello everyone, merry christmas 12:46:49 can someone help me set up a torrent server on my freebsd 14.0 machine with a webui? 12:46:55 i've tried rtorrent, qttorrent and ctorrent but the furthest i've got is a cli with rtorrent that says it can't read the ,rtorrent.rc file even though i did chmod 777 on it 12:47:30 zc4r: have you considered naming it .rtorrent.rc rather than ,rtorrent.rc? 12:47:53 zc4r: i'd used both rtorrent (no webui) and transmission (with webui) from ports with no issues on freebsd. how are you starting rtorrent, and what's the full error / other output? 12:48:37 (actually, rtorrent wasn't quite no issues because if you run it on an nfs mount, it fails to write data because freebsd mmap() is broken on nfs and won't be fixed... but it should be fine on a local zfs/ufs filesystem) 12:48:44 @merry aren't those identical names? 12:48:52 no, one has a comma 12:49:11 (you typed a comma) 12:49:22 oh thats a typo, it's called .rtorrent.rc with a . 12:50:07 i just used sudo pkg install rtorrent and sudo pkg install transmission 12:50:25 do you think it would be wise to install from ports? 12:50:41 pkg is ports, it's just binary packages built from the ports tree. either is fine 12:51:06 you can always use -o import=‹file› if specify a different location if you have your rc in a non-standard location 12:51:43 ok, you have set up transmission with web-ui with no issues. i would like to be able to do that 12:52:44 it should install an rc.d script in /usr/local/etc/rc.d, just enable the service, start it, and then visit the web ui on the appropriate port, which i can't remember offhand because i don't use it anymore 12:53:04 you may need the 'daemon' flavour, i can't remember if the base transmission package includes that... this changed recently for the 4.0 update 12:53:29 ('pkg search transmission', if there's a package with a name like transmission-daemon, make sure that's installed) 12:53:56 i'll start with "pkg install transmission transmission-remote-gui-qt5 transmission-daemon transmision-qt-4" 12:54:30 you don't need the qt packages on the server side. you might want them on the client 12:55:18 also transmission-remote-gui doesn't need to be installed on the server 12:55:25 oh 12:55:35 lemme undo that and try it again 12:55:45 that's an unrelated third-party package that's not related to transmission itself, but again you could install it on the client if you want to use it 12:56:40 so "sudo pkg install transmission transmission-daemon" gives Number of packages to be installed: 27 12:57:09 that's probably fine. i don't know what 'transmission' includes though, maybe just install transmission-daemon and it should pull in everything that's required 12:58:09 sudo service transmission start 12:58:09 transmission already running? (pid=71310). 12:59:01 ok, so you should be able to visit the web ui on whatever port it's running on... you can configure that in the settings.json which again i can't remember the location of (sorry) but find /usr/local -name settings.json should locate it 12:59:19 (if you want to edit settings.json, stop transmission, edit it, then start it again, or it'll be overwritten) 12:59:54 (i think it's something like /usr/local/etc/transmission/home/settings.json) 13:00:21 that's where the online guides seem to fail. the settings.json wasn't where it was supposed to be. i'll search for it 13:01:48 ok it's in /usr/local/etc/transmission/home/settings.json - what should i edit in there to be able to access the webui on my windows machine on the same network? 13:02:19 the internet tells me the default port is 9091, so try http://1.2.3.4:9091/ where 1.2.3.4 is the IP address of the system running transmission-daemon 13:02:59 if you want to change the port, the setting is called "rpc-port" 13:03:09 i get the same as before when i tried this: 403: Forbidden 13:03:27 ah, because it only allows localhost by default 13:03:50 try setting rpc-whitelist to something like "127.0.0.1,192.168.*.*" - but change 192.168.*.* to whatever your local network is 13:04:17 i figured as much but i tried changing a bunch of settings to no avail. i'll try that but it looks like something i tried 13:04:29 make sure you stop the daemon before editing and restart it after 13:04:45 also, https://github.com/transmission/transmission/blob/main/docs/Editing-Configuration-Files.md has a full list of config options 13:04:46 Title: transmission/docs/Editing-Configuration-Files.md at main · transmission/transmission · GitHub 13:05:25 to test, you could set rpc-whitelist-enabled to false and see if that works, but that's rather unsecure 13:06:01 zc4r: you may actually need a url like http://1.2.3.4/transmission/ if it doesn't redirect by default (rpc-url setting) 13:06:11 "rpc-whitelist": "127.0.0.1,192.168.*.*,192.168.1.0/24,192.168.1.161,::1", 13:06:17 still gives me forbidden 403 13:06:33 does it prompt you for a password or just give the error immediately? 13:07:15 error 13:07:24 no user/pass 13:07:28 have a look at the logfile, which should be somewhere in /var/log 13:09:55 i see no transmission log file, but under /var/log/daemon.log i found something suspicious: Dec 14 16:33:20 myrkur ngircd[78733]: ngIRCd 26.1-CHARCONV+IPv6+IRCPLUS+PAM+SSL+SYSLOG+TCPWRAP+ZLIB-amd64/portbld/freebsd14.0 starting ... even though i don't remember setting up ngircd which is an irc client afaik 13:10:43 that's an irc server. no idea about that 13:11:01 oh nvm i remember trying to set up an irc server 13:11:46 although, try 'grep transmission /var/log/daemon.log' 13:11:55 couldn't connect to it, but nevermind that, do you think this line might be at fault: "rpc-whitelist": "127.0.0.1,192.168.*.*,192.168.1.0/24,192.168.1.161,::1", ? 13:12:09 that should be fine as long as the client is in 192.168/16 13:13:23 Dec 26 13:07:57 myrkur transmission-daemon[97935]: port-forwarding.cc:203 Mapped private port 51413 to public port 51413 (port-forwarding.cc:203) 13:13:23 Dec 26 13:10:29 myrkur transmission-daemon[97935]: rpc-server.cc:706 Couldn't bind to 0.0.0.0:9091 after 10 attempts, giving up (rpc-server.cc:706) 13:13:32 those are the newest two 13:13:48 that's odd, did you end up with two copies of transmission running somehow? ps auxw | grep transmission 13:14:33 Dec 26 13:05:55 myrkur transmission-daemon[97935]: tr-lpd.cc:259 Couldn't initialize LPD: Address already in use (48) (tr-lpd.cc:259) 13:14:36 another one 13:14:42 that could be the case 13:14:49 that sounds like you have two running 13:15:04 'service transmission stop' then look at ps and see if there's another one, if so kill it (or them) and start it again 13:16:31 i tried it twice, first stopped transmission, second gave this error: sudo service transmission stop 13:16:31 transmission not running? (check /var/run/transmission/daemon.pid). 13:16:54 what does ps say? 13:18:09 and if i do sudo ps i get 8 instances of getty whatever that is, and su -, -su (csh), su - z, sudo ps, sudo ps and ps 13:18:22 ps auxw | grep transmission 13:18:31 (getty is the daemon that displays the login prompt on the system console) 13:18:50 z 37129 0.0 0.1 43580 15796 - Ss 11:10 0:01.84 transmission-daemon 13:18:50 z 48317 0.0 0.1 43580 15808 - Ss 11:11 0:01.80 transmission-daemon -a 192.168.1.161 13:18:50 z 81963 0.0 0.0 12796 2456 0 S+ 13:18 0:00.00 grep transmission 13:18:55 Gen Z is killing the getty market. 13:19:06 zc4r: kill both of those, and run ps again to make sure they quit 13:19:15 in the hotdog flavoured water 13:19:27 TommyC: getty is trendy again with Wayland since lots of compositors don't support display managers :-) 13:19:56 heh, I haven't been following Wayland tbh 13:20:38 i've been using it for a week or so, i actually quite like it. it reminds me of old Unix systems where the kernel managed the framebuffer (which is basically what DRM is...) 13:20:42 i killed those two, should i try restarting transmission? 13:21:01 zc4r: if you confirmed they're not running anymore, yes, start it again (with 'service') and try connecting to the web ui again 13:21:14 orate 13:21:52 403 forbidden 13:21:54 i used to have an SVR3 system which had a non-X windowing system that ran on top of the system console... if you opened the terminal emulator, it just used the normal text console to display the output (except in a window) but you could display graphics too. it was actually pretty neat 13:22:12 zc4r: check the logfile again 13:23:11 this one seems fishy: Dec 26 13:21:25 myrkur transmission-daemon[8052]: tr-lpd.cc:259 Couldn't initialize LPD: Address already in use (48) (tr-lpd.cc:259) 13:23:40 okay, stop transmission, run 'netstat -an | grep LISTEN' and paste the output somewhere like http://bsd.to 13:23:41 Title: dpaste 13:24:42 i just get a "> " 13:24:54 no nvm 13:25:27 https://bsd.to/Mhdv 13:25:28 Title: dpaste/Mhdv (Plain Text) 13:25:45 there's sockstat for that type of investigation, sockstat -4l 13:25:55 you still have transmission running. do 'ps auxw|grep transmission' again, what does it say? 13:26:18 ps auxw|grep transmission 13:26:19 z 44844 0.0 0.0 12796 2456 0 S+ 13:26 0:00.00 grep transmission 13:26:32 (and there's also pgrep :D) 13:27:02 forgot to sudo, the daemon program was still rnning 13:27:31 ok, kill all copies of it, make sure they're actually dead (by running ps again), then start the service again and try the web ui 13:27:56 we're in business boiz 13:28:11 403 forbidden was defeated 13:28:40 now, how do i make it start on boot? put transmission_enable="YES" in rc.d ? 13:28:46 so, i strongly suggest enabling authentication for the web ui, you can do that with the rpc-authentication-required and rpc-password settings (see https://github.com/transmission/transmission/blob/main/docs/Editing-Configuration-Files.md for info) 13:28:48 Title: transmission/docs/Editing-Configuration-Files.md at main · transmission/transmission · GitHub 13:29:11 zc4r: in /etc/rc.conf, yes, or do 'sysrc transmission_enable=YES' which is an easier way to do it 13:29:49 but if 'service transmission start' worked, you already have that enabled 13:29:56 otherwise you'd have to use 'service transmission onestart' 13:29:57 so could you be more specific in the authentication proceedings? 13:30:12 yes such was the case 13:30:29 set rpc-authentication-required to true, set rpc-password to a password, then start transmission and it'll prompt you for the password. remember to stop it before editing settings.json or it'll overwrite it 13:30:52 (the user is always 'transmission', you can only configure the password) 13:31:17 those settings are in the settings.json file right? 13:31:29