Jump to content

MrChunky

Members
  • Content Count

    72
  • Joined

  • Last visited

  • Days Won

    1

MrChunky last won the day on April 21 2018

MrChunky had the most liked content!

Community Reputation

5 Neutral

About MrChunky

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Was the feature request submitted for this finally?
  2. Seems like it may be my configuration that is the problem rather than the wp container. Thanks for the suggestions in any case! I will keep going, if I'll figure it out I'll post...
  3. I deleted the mariaDB folder and word-press folder... Am I missing a 3rd folder to delete?
  4. Hey Kru-x, Thanks for the prompt response as usual NPM was being weird... for some reason the certificates always get screwed up for me when I use NPM. I get some sort of cant access the folder with certificates error in the log. Anyways, I switched to linuxserver lets encrypt container, which has been working fine for years... Now I have too many redirects error when I try to go to the root or any non admin pages. I can reach every admin page on the wp site, if I put in the path directly or navigate within it. I just cannot get the root or the pages to load... I get ERR_TOO_MANY_REDIRECTS, from both inside and outside my LAN. I am using domain, I went through the installation process while accessing it with www.example.com. so in the general setting the site url is www.example.com from the begining. Yes I can thought the domain, but I have to put in www.example.com/wp-admin to reach it. Already did that, that's how I installed it.
  5. I am seeing some really strange behavior... I have wordpress setup and working with nginx proxy manager. I can reach all the pages except for the root. When I input the root address e.g. www.example.com I get ERROR_CONNECTION_TIMEOUT and the address displays as www.example.com:8080. The strange thing is that my port for wordpress is not 8080. In fact, none of the used ports are 8080. I was wondering if someone could shine a light on what going on here...
  6. Hi Maggi, Could you post your logs output and a screenshot of your config page for the docker or the run command that appears when you start it.
  7. Hi emilp, As Squid mentioned, the update is reliant on proper tag (beta/ latest) maintenance by storj. All I did was create a template that allows you to use the official storj docker image. As you pointed out the beta tag is still in the documentation and provides the latest beta versions. So when it is updated, UnRaid docker will update the container on a schedule, if you have the plugin, or you can manually update it. Also in the storage node GUI it mentions that the minimum allowed is 1.1.0, so i think you should be fine for a while.
  8. I would guess that the --mount commands are failing, possibly because the folders are not found. Could you check the folder structures are indeed in place for both mount commands and that the relevant files are in there? This is my how my run command looks: run -d --name='StorjNode-V3' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'WALLET'='xxx' -e 'EMAIL'='xxx' -e 'ADDRESS'='xxx:28968' -e 'BANDWIDTH'='10000TB' -e 'STORAGE'='12TB' -p '28968:28967/tcp' -p '14002:14002/tcp' --mount type=bind,source="/mnt/user/appdata/storj_cert/storj/identity/storagenode/",destination=/app/identity --mount type=bind,source="/mnt/user/storjv3/",destination=/app/config 'storjlabs/storagenode:beta' Another is that my net is bridge, not host. But I doubt this is an issue.
  9. Overview: Support for Docker image Storj v3 storage node. Application: https://storj.io/ Docker Hub: https://hub.docker.com/r/storjlabs/storagenode GitHub: https://github.com/storj/storj Documentation: https://documentation.storj.io/ Storj forum: https://forum.storj.io/ 19/02/2020 - Updated the template with some clarifications and changed network to bridge.
  10. Hey people from the past. In my experience of the last 2 days 😀 of trying to sort out this issue, a dummy plug is very important for getting any kind of gaming on a headless vm going. No amount of rom dumps or combinations of settings made a difference until I plugged in a monitor. However, I did also broadly follow the advice in this thread before plugging in the monitor. In case anyone is looking at this in the future.
  11. It dawned on me a few days ago that the stress from trying to run this thing is not worth the 5 dollars I am gonna make on it per month... I would still have a go at it to support the idea, but as @nuhll said, I will chill for now until the issues are sorted out a bit more.
  12. Seems we are not the only ones: https://ideas.storj.io/ideas/V3-I-30
  13. Please vote for the storj v3 node to be officially supported on Unraid by storj: https://ideas.storj.io/ideas/V3-I-43
  14. I got this error with mine: 2019-08-26T11:35:44.215Z [34mINFO[0m process/exec_conf.go:229 Configuration loaded from: /app/config/config.yaml 2019-08-26T11:35:44.237Z [34mINFO[0m kademlia/config.go:78 Operator email: xxx 2019-08-26T11:35:44.237Z [34mINFO[0m kademlia/config.go:92 operator wallet: xxx 2019-08-26T11:35:44.762Z [31mERROR[0m storagenode/main.go:164 Failed to initialize telemetry batcher: process error: telemetry disabled main.cmdRun /go/src/storj.io/storj/cmd/storagenode/main.go:164 storj.io/storj/pkg/process.cleanup.func1.2 /go/src/storj.io/storj/pkg/process/exec_conf.go:262 storj.io/storj/pkg/process.cleanup.func1 /go/src/storj.io/storj/pkg/process/exec_conf.go:280 github.com/spf13/cobra.(*Command).execute /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:762 github.com/spf13/cobra.(*Command).ExecuteC /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:852 github.com/spf13/cobra.(*Command).Execute /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:800 storj.io/storj/pkg/process.Exec /go/src/storj.io/storj/pkg/process/exec_conf.go:72 n /go/src/storj.io/storj/cmd/storagenode/main.go:296 runtime.main /usr/local/go/src/runtime/proc.go:200 2019-08-26T11:35:44.781Z [31mFATAL[0m process/exec_conf.go:286 Unrecoverable error {"error": "Error creating tables for master database on storagenode: migrate: creating version table failed: migrate: file is not a database\n\tstorj.io/storj/internal/migrate.(*Migration).Run:106\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).CreateTables:230\n\tmain.cmdRun:167\n\tstorj.io/storj/pkg/process.cleanup.func1.2:262\n\tstorj.io/storj/pkg/process.cleanup.func1:280\n\tgithub.com/spf13/cobra.(*Command).execute:762\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:852\n\tgithub.com/spf13/cobra.(*Command).Execute:800\n\tstorj.io/storj/pkg/process.Exec:72\n\tmain.main:296\n\truntime.main:200", "errorVerbose": "Error creating tables for master database on storagenode: migrate: creating version table failed: migrate: file is not a database\n\tstorj.io/storj/internal/migrate.(*Migration).Run:106\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).CreateTables:230\n\tmain.cmdRun:167\n\tstorj.io/storj/pkg/process.cleanup.func1.2:262\n\tstorj.io/storj/pkg/process.cleanup.func1:280\n\tgithub.com/spf13/cobra.(*Command).execute:762\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:852\n\tgithub.com/spf13/cobra.(*Command).Execute:800\n\tstorj.io/storj/pkg/process.Exec:72\n\tmain.main:296\n\truntime.main:200\n\tmain.cmdRun:169\n\tstorj.io/storj/pkg/process.cleanup.func1.2:262\n\tstorj.io/storj/pkg/process.cleanup.func1:280\n\tgithub.com/spf13/cobra.(*Command).execute:762\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:852\n\tgithub.com/spf13/cobra.(*Command).Execute:800\n\tstorj.io/storj/pkg/process.Exec:72\n\tmain.main:296\n\truntime.main:200"} storj.io/storj/pkg/process.cleanup.func1 /go/src/storj.io/storj/pkg/process/exec_conf.go:286 github.com/spf13/cobra.(*Command).execute /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:762 github.com/spf13/cobra.(*Command).ExecuteC /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:852 github.com/spf13/cobra.(*Command).Execute /go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:800 storj.io/storj/pkg/process.Exec /go/src/storj.io/storj/pkg/process/exec_conf.go:72 n /go/src/storj.io/storj/cmd/storagenode/main.go:296 runtime.main /usr/local/go/src/runtime/proc.go:200 Looks like database is unhappy in some way as well. I got the following response from support: I am not convinced this is true... as the error is not to do with failed audits, but with database access. I am in a situation where I cannot even start the container due to this error. As for the stop time, this can be added to extra parameters afaik. I will experiment with it, since I don't have much to loose.