live4soccer7
-
Posts
422 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by live4soccer7
-
-
I'm not sure what I'm doing wrong here. I added my mnemonic phrase through chia keys add, however I still get this for the wallet.
if I do chia wallet show it shows stuff about my wallet and also provides the fingerprint id as well.
if i run: chia start farmer it stays that everything is already running.
I'm just a bit confused by the wallet exception and the connection error. Any insight on this?
-
I ended up going with the H310 with the breakout cables. It was hard to beat that added capacity for $35.
-
Any idea what may be causing the issue? Everything literally worked for about the last year and I can't seem to find anything that changed to cause this to not work anymore. Any ideas?
I am able to access nextcloud, btwarden, and everything else I have setup except onlyoffice. I am on onlyoffice document server 6.0. It is its own separate docker. Again, it literally has been working great for the last year or so.
==> /var/log/onlyoffice/documentserver/docservice/out.log <== [2021-05-07T20:56:44.069] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode [2021-05-07T20:57:23.671] [WARN] nodeJS - Express server starting... [2021-05-07T20:57:23.674] [WARN] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/docs/latest/api/fs.html#fs_availability [2021-05-07T20:57:23.782] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode [2021-05-08T20:15:28.620] [WARN] nodeJS - Express server starting... [2021-05-08T20:15:28.622] [WARN] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/docs/latest/api/fs.html#fs_availability [2021-05-08T20:15:28.755] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode [2021-05-08T20:16:06.991] [WARN] nodeJS - Express server starting... [2021-05-08T20:16:06.995] [WARN] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/docs/latest/api/fs.html#fs_availability [2021-05-08T20:16:07.107] [WARN] nodeJS - Express server listening on port 8000 in production-linux mode ==> /var/log/onlyoffice/documentserver/metrics/err.log <== ==> /var/log/onlyoffice/documentserver/metrics/out.log <== gauges: { 'statsd.timestamp_lag': 0 }, timer_data: {}, counter_rates: { 'statsd.bad_lines_seen': 0, 'statsd.packets_received': 0, 'statsd.metrics_received': 0 }, sets: {}, pctThreshold: [ 90 ] } 8 May 20:15:27 - [904] reading config file: ./config/config.js 8 May 20:15:27 - server is up INFO ==> /var/log/onlyoffice/documentserver/nginx.error.log <== ==> /var/log/onlyoffice/documentserver/spellchecker/err.log <== ==> /var/log/onlyoffice/documentserver/spellchecker/out.log <== [2021-05-07T20:54:05.768] [WARN] nodeJS - Express server starting... [2021-05-07T20:54:05.827] [WARN] nodeJS - Express server listening on port 8080 in production-linux mode [2021-05-07T20:56:42.939] [WARN] nodeJS - start cluster with 1 workers [2021-05-07T20:56:42.953] [WARN] nodeJS - worker 934 started. [2021-05-07T20:56:43.489] [WARN] nodeJS - Express server starting... [2021-05-07T20:56:43.536] [WARN] nodeJS - Express server listening on port 8080 in production-linux mode [2021-05-08T20:15:27.633] [WARN] nodeJS - start cluster with 1 workers [2021-05-08T20:15:27.640] [WARN] nodeJS - worker 955 started. [2021-05-08T20:15:28.244] [WARN] nodeJS - Express server starting... [2021-05-08T20:15:28.357] [WARN] nodeJS - Express server listening on port 8080 in production-linux mode ==> /var/log/onlyoffice/documentserver/metrics/out.log <== Flushing stats at Sat May 08 2021 20:25:27 GMT+0000 (Coordinated Universal Time) { counters: { 'statsd.bad_lines_seen': 0, 'statsd.packets_received': 0, 'statsd.metrics_received': 0 }, timers: {}, gauges: {}, timer_data: {}, counter_rates: { 'statsd.bad_lines_seen': 0, 'statsd.packets_received': 0, 'statsd.metrics_received': 0 }, sets: {}, pctThreshold: [ 90 ] } -
I'll just be using Sata drives for the NAS. Prob some WD Red drives.
-
Would it be worth going for a SAS3 version if I were to attach 8 drives to two SAS ports? I'd imagine the throughput could be slowed down a bit by that. Perhaps it wouldn't really matter with the speeds that Unraid can/can't do.
-
It looks like the H310 or the M1015 would probably be the best choice as they can be had for cheaper than some of the other similar models. The "breakout" cables are what I would need since I don't have a backplane.
Any preference over the H310 vs the M1015?
-
Thanks! looks like I need a little education here. I'll get read up and post back if necessary
Thanks a ton
-
I do have spare slots. I was asking for suggestions on which one to get.
-
What would be the go to "expander" for this board? It supports 14 drives as it sits with the onboard controller flashed, but I need to more drives. I've read about H310, some LSI, An Intel 1015 (IIRC), etc.... is there one that stands out as a better option?
Thanks for any suggestions.
-
Thanks! I'll check it out.
-
I've been using the setup from spaceinvader for quite some time. It uses the external only office docker with nextcloud. I am on onlyoffice 6.0 as there were issues with the update past that. It has been working over a year and now all the sudden only office just spins/loads when I try to open a document. Nothing was changed that I know of. There could have been an update on the nextcloud docker. I don't see anything in the logs on the docker page within unraid.
Has anyone else experience this of of lately with no apparent manual changes to configurations?
-
Anyone get this error when updating? I haven't updated in probably a few years, until now.
started connecting [20200528-11:17:41] [INFO ] lib_mod_log_peer: xrdp_pid=144 connected to X11rdp_pid=50 X11rdp_uid=99 X11rdp_gid=100 client_ip=127.0.0.1 client_port=35522 connected ok [20200528-11:17:41] [DEBUG] xrdp_mm_connect_chansrv: chansrvconnect successful [20200528-11:17:41] [DEBUG] returnvalue from xrdp_mm_connect 0 lib_mod_process_message: type 2 len 0 lib_send_client_info: xrdp_wm_login_mode_changed: login_mode is 3 [20200528-11:17:41] [INFO ] The following channel is allowed: cliprdr (0) [20200528-11:17:41] [INFO ] The following channel is allowed: rdpsnd (1) [20200528-11:17:41] [INFO ] The following channel is allowed: rdpdr (2) [20200528-11:17:41] [DEBUG] The allow channel list now initialized for this session [20200528-11:17:47] [INFO ] An established connection closed to endpoint: 127.0.0.1:35522 - socket: 8 xrdp_mcs_disconnect - socket closed [20200528-11:17:47] [DEBUG] xrdp_mm_module_cleanup [20200528-11:17:47] [INFO ] An established connection closed to endpoint: 109.112.47.46:12148 - socket: 11 [20200528-11:17:47] [INFO ] An established connection closed to endpoint: 109.112.47.46:12148 - socket: 12 xrdp:xrdp_encoder [1551967640]: xrdp_encoder_delete: [20200528-11:17:47] [ERROR] Listening socket is in wrong state we terminate listener -
Try port 443. I know spaceinvader says to change it, however that is the only way I could get mine to work as well. It was weird as it didn't make sense to me because I changed the port in the conf files, but it was like it wouldn't listen to what I was setting. It was like there was another setting somewhere defining which port nextcloud was listening on. I also left the bitwarden on the default port too. I was able to get both working.
-
15 minutes ago, saarg said:
You can access it via the IP, but you will be redirected to the domain when the page loads.
My question to this would be, would it then use the internet for viewing etc... or would it work over the local LAN. Right now it appears to be utilizing the internet and not the local LAN when accessing it from a local machine.
-
8 minutes ago, Otacon said:
I have fixed my problem with SMTP. Don't forget to save your settings before trying to send a test email.
Yes, I always hit save after inputting new settings and then sending a test email after it has saved. What did you do to fix the problem? Are you using port 465 or 587 and do you have TLS checked or not?
-
I'm having some issues setting up smtp on bitwardenrs. I have a dedicated gmail account that I use for another service. I have enabled 2fa and created an app key/password and utilized that within bitwarden, just as I have with my other application (node-red). No matter what I try, it will not send a test email. I thought maybe it was gmail, so I went ahead and created a yahoo account and the result was the same. I just installed the latest version of bitwardenrs for the first time a couple weeks ago and have finished setting it up now. Here is the error I'm receiving.
Has anyone else had this experience and if so, what did you do to resolve it?
I have tried 587 TLS and 465 without TLS and every combination in between.
[CAUSE] Io( Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable", }, ) [2020-04-30 09:05:48][response][INFO] POST /admin/test/smtp (test_smtp) => 400 Bad Request [2020-04-30 09:05:53][request][INFO] POST /admin/config/ [2020-04-30 09:05:53][response][INFO] POST /admin/config (post_config) => 200 OK [2020-04-30 09:05:54][request][INFO] GET /admin [2020-04-30 09:05:54][response][INFO] GET /admin (admin_page) => 200 OK [2020-04-30 09:06:00][request][INFO] POST /admin/test/smtp/ [2020-04-30 09:06:01][lettre::smtp][INFO] connection established to 188.125.73.26:465 [2020-04-30 09:06:02][error][ERROR] LetreErr. [CAUSE] Permanent( Response { code: Code { severity: PermanentNegativeCompletion, category: Unspecified3, detail: Five, }, message: [ "5.7.0 (#AUTH005) Too many bad auth attempts.", ], }, ) [2020-04-30 09:06:02][response][INFO] POST /admin/test/smtp (test_smtp) => 400 Bad Request -
^ definitely a good question.
I have another quick question. Once SSL/Letsencrypt is setup and working, should I be able to access the docker at the local address:port (192.168.1.110:444) or will it only be accessible via the URL/Domain that was setup?
-
11 minutes ago, saarg said:
You are messing around with settings you don't need to change.
There is no mention of changing the port in the proxy conf, so that means don't change the port! It's talking on the internal docker network, so port mapping doesn't apply. 443 is the correct port.
Leave the nextcloud config at 444, as that is for accessing locally using IP.
As for the default file you keep on insisting to edit, don't! There is nothing you have to comment or uncomment to make either subdomain or subfolder working.
I'm not sure what to say. I put everything back to the way it downloaded (unchanged) with the exception of commenting out the subfolder aspect in the default conf file within letsencrypt. At that point everything worked as expected and I have also set up to other dockers on subdomains without issues and without having to edit any files other than changing servername to match my subdomain.
-
One thing to note, I did change the ports back to 443. I wanted to change back to 444 or something different, however when I did this by changing it in the nextcloud docker container (444), the nextcloud config.php, and the nextcloud.subdomain.conf, I was presented with a 502 bad gateway. Is there another file that would need adjusted that I'm simply not seeing?
-
I got it! It just hit me. It seemed like the subdomain.conf was not getting read, so I though well maybe the subfolder inclusion in the letsencrypt default conf was actually over-riding or taking priority/preference over the subdomain.conf inclusion. It came with both uncommented. I commented out the subfolder and voila.
# enable subfolder method reverse proxy confs
#include /config/nginx/proxy-confs/*.subfolder.conf;
Again, this is in: letsencrypt/nginx/site-confs/default
I suppose it is possible that I uncommented this somehow without realizing it, but I'm pretty sure it came with both uncommented.
-
I just changed the container port to 443, adjusted nextcloud.subdomain.conf to 443 and same with nextcloud's config.php. The result was the same. It is simply loading the letsencrypt index.html, so nexcloud's proxy is not getting passed.
In the readme within proxy-confs for letsencrypt, the following lines standout to me. Is there really nothing to do within the default site config?
### Configure your default site config
Make sure that your default site config contains the following lines in the appropriate spots as seen in the default version:
1) For subfolder methods: `include /config/nginx/proxy-confs/*.subfolder.conf;`
2) For subdomain methods: `include /config/nginx/proxy-confs/*.subdomain.conf;` -
50 minutes ago, saarg said:
Didn't see it was commented out.
You have created a custom network that both nextcloud and letsencrypt use, right? If so you have not followed the instructions at the top of the proxy conf. You have changed the port from 443 to 444. That is something you should not do. Change it back to 443 and restart letsencrypt.
Are you referring to the container port? I have changed the port that the nexcloud container uses to 444 (why my subdomain.conf and config.php reflect this). You're saying to leave it at 443 and then adjust the subdomain.conf and config.php back to 443 for the container port? I still don't think this would be the issue because I tried setup the subdomain for sonarr with lets encrypt as well and my results are the exact same as with nextcloud.
Yes, I have created a custom network that nextcloud and letsencrypt are on.
I really appreciate everyone's time on this. I have been pulling my hair out over this for the last week and a half.
-
41 minutes ago, saarg said:
Remove the one you added. There is no need to edit anything in the default file to get proxy confs working. All you have to do is to remove the .sample part, edit the file if it is mentioned to do so in the top of the file and restart letsencrypt. Did you restart letsencrypt?
It is commented out, so essentially no change. You can see where it is commented out. Yes, I restarted everything. Otherwise everything is 100% stock in this file. I commented out my addition, so it has no effect.
-
7 minutes ago, Tucubanito07 said:
Let me look at my Letsencrypt and config file and get back with you. I am no expert but maybe together we can figure this out. I currently at work. Once I am done I’ll try to send you my config files so you can mimic them n
Thank you very much. I have definitely expended many many many hours getting this setup, so it isn't a lack of effort. I am no expert either. I think that something has changed in the latest versions released by LSIO as I'm seeing my stock files included are just a little different than others' files on the thread. Hopefully, with your configs I may be able to piece something together.
Thanks a ton
[Support] Partition Pixel - Chia
in Docker Containers
Posted
I don't think you'll need to open ports on your router.
I was able to get my issue resolved. I added the mneomic to text to the respective location in the docker setup. I didn't think that would be necessary since I added the phrase in the cli.