|
<< Click to Display Table of Contents >> Navigation: Telegram > 2018 > 12 > 18 > Telegram_2018-12-18T11 |
2018-12-18T11:01:04
When you get the 403 error, can you use the debugger (ctrl-shift-J in chrome, and I think FF too) and look at the headers and see what server is sending the 403? IW should not send a 403, it seems like there is something else intercepting the call.
2018-12-18T11:01:20
It will be in the headers tab.
2018-12-18T11:01:24
type: link 192.168.10.8/MyIWApp/ error 403: forbidden : access refused
2018-12-18T11:02:32
type: link 192.168.10.8:8888/MyIWApp/ waiting delay exceeded
2018-12-18T11:02:48
When its IW issuing the errors, normally you should see something like this instead. So we need to find out who is sending the 403.
2018-12-18T11:03:00
Do you have a proxy?
2018-12-18T11:03:49
Can you try this link in a browser ON the server?
type: link http://192.168.10.8:8888/MyIWApp/
Same results or different?
2018-12-18T11:06:13
Ce site est inaccessible type: link 192.168.10.8 a mis trop de temps à répondre.
Effectuez une recherche Google sur 192 168 8888 MyIWApp.
ERR_CONNECTION_TIMED_OUT
2018-12-18T11:06:32
It is the chrome message: delay exceeded
2018-12-18T11:33:45
I tried on a second server. it works with type: bot_command /gui but it doesn't as service
2018-12-18T11:34:09
the IP is type: link http://188.165.192.48:8888/MyIWApp/
2018-12-18T11:35:20
Sorry was called away. I am back now.
2018-12-18T11:35:53
ok it looks like its a time out and chrome is masking it with a 403? Anyway, its likely the firewall.
2018-12-18T11:35:54
try this
2018-12-18T11:36:13
from server first do
telnet type: link 127.0.0.1 8888
2018-12-18T11:36:38
see if anything happens or it gives error. Success may be a simple waiting. if so, press enter and see if it responds.
2018-12-18T11:37:17
oh wait, it works as GUI but not service? See if there is a .log file.
2018-12-18T11:37:38
Services run as a different non interactive user, if your code needs special permissions this can often cause start up errors.
2018-12-18T11:39:28
or an .err... look where the exe is for .log or .err
2018-12-18T11:39:40
When its as a service you can reach it on 127?
2018-12-18T11:40:26
We can also try with guess, that is compile guess demo which I know doesnt need any special libraries or permissions. If it deploys ok, then its not a firewall issue but something in your app that does not like being run as a service.
2018-12-18T11:44:17
where do I find guest demo
2018-12-18T11:44:19
if possible, can you list:
-What works and what doesnt
ie - 127 as service, yes or no,, etc...
2018-12-18T11:44:38
guess I think ships as part of the install, but if not its in our demos which are linked on our download page.
2018-12-18T11:46:50
it's not there
2018-12-18T11:49:57
on the local server :
/ gui works
as service works
type: link http://192.168.10.8:8888/MyIWApp/$/Start delay exceeded
on the web server
2018-12-18T11:50:39
type: link https://github.com/Atozed/IntraWeb/tree/master/XIV/Delphi/Guess
Its there. You can take the SA one and convert it for http.sys, or look in the 15 demo tree (This is 14) and there might be a http.sys ready one.
2018-12-18T11:50:42
type: bot_command /gui works
as service doesn't
type: link http://188.165.192.48:8888/MyIWApp/$/start delay exceeded
2018-12-18T11:51:16
so locally (your dev pc?) both gui and service work right? Thats the 192 one?
2018-12-18T11:52:05
on web server (a web host I assume?) gui works, but service doesnt? Is that correct?
On this web server, does the GUI work with 188 or only 127?
2018-12-18T11:52:30
ie when running as GUI, does it work remotely or only locally on the server?
2018-12-18T11:56:25
on web server, I it works for type: bot_command /gui as service with 127 and 188 but it doesn't from outside
2018-12-18T11:57:08
as GUI it fails or works from outside using 188?