They are, we slowed the push and cache so the site dosnt blow up like every expansion. Give it a good 10 mins, and it should be showing :) if not please bump this
You can use instead of the card name between the brackets to get the card you intended to post. The correct id for DK obtainable Frostmourne is 63047.
That fixes the issue for that card but its painful to use that code whenever I want to write Frostmourne, and it doesn't solve Army of the Dead. Where is this information shown otherwise?
the url on every card page. The problem is the system puts real cards > tokens, However both are tokens in this case.
Can you attach the logs from innkeeper itself? (you have attached the install log, but would like to see the main innkeeper apps logs) you can find where to find them in our FAQ
Hey, it looks like you have it set when your computer goes to sleep, it disabled some things from happening in the background. In this case, the front end of innkeeper is trying to ping the backend, and while its asleep w/e setting is set, it fails the ping, thing the backend must have crashed, and closes
[2017-07-29 11:11:49.116] ping fail [2017-07-29 11:11:51.116] ping fail [2017-07-29 11:11:53.124] App process went away, exiting [2017-07-29 11:11:53.132] ping fail
one thing we could possibly do, is add a setting that will ignore ping checks, as im not sure what setting needs to be changed in windows to fix that.
the only thing I could think to try is going to C:\Users\owner\AppData\Roaming\InnkeeperUI\config.json and deleting that file (with innkeeper fully closed) and then launching innkeeper again.
[2017-07-19 08:32:04.642] Uncaught exception in main.js! [2017-07-19 08:32:04.649] Error: EPERM: operation not permitted, open 'C:\Users\owner\AppData\Roaming\InnkeeperUI\config.json' at Error (native)
this is an odd one, it looks like its not allowed to open its own config. (maybe some anti virus is stil ltrying to prevent innkeeper from reading its config)
Try this, in the system tray make sure innkeeper is fully closed out. (and check task manager) then, run innkeeper as admin from the shortcut (dont re-install) and see if that lets it load its config
This is something we need to fix, but there is a "confirm" button thats being rendered off the screen, if you can drag it up, or turn off screen scailing, youll be able to click it
3
They are, we slowed the push and cache so the site dosnt blow up like every expansion. Give it a good 10 mins, and it should be showing :) if not please bump this
1
Try now
1
0
Can you attach the logs from innkeeper itself? (you have attached the install log, but would like to see the main innkeeper apps logs) you can find where to find them in our FAQ
0
Hey, it looks like you have it set when your computer goes to sleep, it disabled some things from happening in the background. In this case, the front end of innkeeper is trying to ping the backend, and while its asleep w/e setting is set, it fails the ping, thing the backend must have crashed, and closes
one thing we could possibly do, is add a setting that will ignore ping checks, as im not sure what setting needs to be changed in windows to fix that.
0
0
the only thing I could think to try is going to C:\Users\owner\AppData\Roaming\InnkeeperUI\config.json and deleting that file (with innkeeper fully closed) and then launching innkeeper again.
0
thanks!
this is an odd one, it looks like its not allowed to open its own config. (maybe some anti virus is stil ltrying to prevent innkeeper from reading its config)
Try this, in the system tray make sure innkeeper is fully closed out. (and check task manager) then, run innkeeper as admin from the shortcut (dont re-install) and see if that lets it load its config
0
the reason is
[2017-07-26 17:42:27.800] [System] Display 1: 1280x720 (Primary)
[2017-07-26 17:42:27.802] [System] Screen scaling factor is 1.50x
This is something we need to fix, but there is a "confirm" button thats being rendered off the screen, if you can drag it up, or turn off screen scailing, youll be able to click it
0
until we have a new system in place, ill see if I can swap this back on for you
0
that should be coming very soon :)
0
Cant help without any logs attached :)
9
hshsjsjd
3
We have the solution on the way, was an https issue
2
test test rest test test