Permissions Rails 5服务器问题（Windows 10）

这里是RubyonRails的新手，我刚刚在UbuntuShell上的Windows10Bash上重新安装了Ruby&Rails。我似乎在启动Rails服务器时遇到了问题。已经检查了该问题的其他线程，但其他所有人都在使用OSX：希望有人能帮忙

当运行轨道时

root@TEAMROCKETHQ:~/newapp# rails s
/root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/railties-5.0.2/lib/rails/app_loader.rb:40: warning: Insecure world writable dir /root/.rbenv/versions in PATH, mode 040777
=> Booting Puma
=> Rails 5.0.2 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
Puma starting in single mode...
* Version 3.8.0 (ruby 2.4.0-p0), codename: Sassy Salamander
* Min threads: 5, max threads: 5
Environment: development
* Listening on tcp://localhost:3000
Use Ctrl-C to stop

对于第一行问题，我尝试：

sudo chmod 775 /usr/local

看起来它什么也没做。也许我读错了，但我不知道。。。当我转到localhost:3000时，它返回以下错误：

=> Booting Puma
=> Rails 5.0.2 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
Puma starting in single mode...
* Version 3.8.0 (ruby 2.4.0-p0), codename: Sassy Salamander
* Min threads: 5, max threads: 5
Environment: development
* Listening on tcp://localhost:3000
Use Ctrl-C to stop
2017-03-09 23:17:26 -0600: Read error: #<Errno::EINVAL: Invalid argument - getsockopt(2)>
/root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/puma-3.8.0/lib/puma/server.rb:124:in `getsockopt'
/root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/puma-3.8.0/lib/puma/server.rb:124:in `closed_socket?'
/root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/puma-3.8.0/lib/puma/server.rb:563:in `handle_request'
/root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/puma-3.8.0/lib/puma/server.rb:425:in `process_client'
/root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/puma-3.8.0/lib/puma/server.rb:289:in `block in run'
/root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/puma-3.8.0/lib/puma/thread_pool.rb:120:in `block in spawn_thread'

网页：

本地主机页不工作

localhost当前无法处理此请求

HTTP错误500

这是因为puma 3.8.0

将gem'puma'、'3.7.1'放入gem文件中，然后重新捆绑安装

---

然后在3.8.0版上卸载puma，等待修复。

修复了我原来的问题，但出现了另一个问题。~>3.8.0更新后，有几个问题。此问题的参考号：，@Everywhere肖恩