-
Notifications
You must be signed in to change notification settings - Fork 285
Config File is Malformed #738
Comments
I can confirm this is happening on a new Windows 10 64 installation (tried 64 & 32 bit versions). App has never been installed on this PC before. If there are any debug logs etc you would like me to post just ask and tell me where to find them. Tried starting OpenBazaar as Admin. No difference. |
same issue - same OS {win10 64} can't connect to zcash due to malformed config OpenBazaar Server v0.11.1 [[OB-SERVER]] [STDOUT] 16:10:34.116 [Execute] [ERROR] Config file is malformed [[OB-SERVER]] [STDERR] Config file is malformed [LOCAL-SERVER] Server exited with code: 1 |
Same issue here........ I'm running Windows 10 Pro 64-bit, here is the output from debug: OpenBazaar Server v0.11.1 [[OB-SERVER]] [STDERR] Config file is malformed [[OB-SERVER]] [STDOUT] 12:04:20.972 [Execute] [ERROR] Config file is malformed [LOCAL-SERVER] Server exited with code: 1 |
Has anyone found a solution to this problem? I am also on a Windows 10 Pro 64-bit and I have been unable to get the app running on this machine. I was able to download and run the program on a mac but was oddly unable to upload any photographs of listings or my store profile. Looking to solve my server issue on windows now, any suggestions appreciated |
Hello all. If this is still relevant, please post a copy of your config via a new request at https://openbazaar.zendesk.com/ and reference this issue. Also please include if you have any details about the steps leading up to the failure if you believe its relevant. Your config can be found at: Windows: C:\Users[Username]\OpenBazaar2.0*\config OSX: ~/Library/Application Support/OpenBazaar2.0*/config Linux: ~/.openbazaar2.0*/config *there may be some additional value here depending on your configuration |
Seems this problem is related to editing config in the terminal. |
Possible issues:
Tested on: Bug results in API and security difficulties. |
Multiple users have reported an issue with the server crashing on start due to a malformed config file.
This appears to happen on new installs, there was at least one report of it happening on an update.
The text was updated successfully, but these errors were encountered: