hexo d 的时候出现如下错误,不知道怎么结局
fatal: unable to access 'https://github.com/769824456/769824456.github.io.git/': Failed to connect to github.com port 443: Timed out
FATAL Something's wrong. Maybe you can find the solution here: http://hexo.io/docs/troubleshooting.html
Error: fatal: unable to access 'https://github.com/769824456/769824456.github.io.git/': Failed to connect to github.com port 443: Timed out
at ChildProcess.<anonymous> (E:\NoteData\hexo\node_modules\hexo-util\lib\spawn.js:37:17)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at ChildProcess.cp.emit (E:\NoteData\hexo\node_modules\cross-spawn-async\lib\enoent.js:37:29)
at maybeClose (internal/child_process.js:850:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
FATAL fatal: unable to access 'https://github.com/769824456/769824456.github.io.git/': Failed to connect to github.com port 443: Timed out
Error: fatal: unable to access 'https://github.com/769824456/769824456.github.io.git/': Failed to connect to github.com port 443: Timed out
at ChildProcess.<anonymous> (E:\NoteData\hexo\node_modules\hexo-util\lib\spawn.js:37:17)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at ChildProcess.cp.emit (E:\NoteData\hexo\node_modules\cross-spawn-async\lib\enoent.js:37:29)
at maybeClose (internal/child_process.js:850:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
hexo d is the command to publish to github. Visually, your error is that the link to github times out. The default port of https is 443, which may be due to network speed. You can try to access github.com first. Then post it
Make sure you have set up git on your computer properly or try to use HTTPS repository URL instead.
Use ssh link, generate the key locally and add it to your project
The error shows you that the connection to github has timed out. Use the following command to check whether you can connect to github:
If text similar to the red box appears, it means you can connect to github. If not, there may be a problem with your configuration. Please check your configuration carefully. It is best to use the SSH address for the configured Github remote warehouse address.
My configuration looks like this: