Is there any possibility to debug a Website remotely, which is open on an LG TVs Browser? I found some solutions to debug my own WebOS App with Visual Studio Code, but i want to debug the WebOS internal Browser.
The Reason for this is, that there is a website which has issues only when dsiplaying it on the LG internalal Webbrowser.
I also tried it with the "ares-inspect" command from the WebOS CLI, but i think its only possible to debug your own App with the known AppID.
I hope someone can help me out here ...
Edit 1:
In the meantime i figured out the AppID of the Internal Browser and tried to connect via ares to it:
ares-inspect -a com.webos.app.browser -d tv
Session#forward() failed forwarding client localPort: 0 (inCnx.remotePort: 65530 )=> devicePort: 9998
ares-inspect WARN Session#forward() failed forwarding client localPort: 0 => devicePort: 9998
Session#forward() failed forwarding client localPort: 0 (inCnx.remotePort: 65531 )=> devicePort: 9998
ares-inspect WARN Session#forward() failed forwarding client localPort: 0 => devicePort: 9998
Application Debugging - http://localhost:49576
When i open the URL (http://localhost:49576) in (for my WebOS version corresponding) Chromium Browser i only get this Screen:
Related
I have run below command for expose the application to external URL for viewing in mobile devices
npm run dev -- --host
VITE v3.1.8 ready in 618 ms
➜ Local: http://localhost:xxx/
➜ Network: http://xxx.xxx.x.xx:xxxx/
➜ Network: http://xxx.xxx.xxx.x:xxxx/
The network URL is working fine when I open it in my desktop but it can't be opened in mobile devices and show "Safari could not open the page because the server stopped responding" after a period of time.
This might be late but I encountered the same thing right now. You just need to turn off your firewall on public network. Windows security -> Firewall network -> Public network.
I have installed browsersync using command npm install -g browser-sync in windows 10 x64. nodejs version 10.11.0 browsersync version 2.26.3
everything is working fine in desktop. but when i try to access http://192.168.56.1:3000 from mobile device using same wifi, i get "this site can't be reached"
i have installed another tool named dev-ip which returns this in powershell:
[ '192.168.56.1', '192.168.0.120' ]
the ip series 192.168.0.120 used to work fine in my mobile devices.
now, how to use the ip 192.168.0.120 instead of 192.168.56.1 in browsersync globally?
Just specify the host in your configuration that you want the server to run on.
Eg. In you case it would be
host: "192.168.0.120"
You can refer to the link below for more information.
https://www.browsersync.io/docs/options#option-host
Hi, guys. This is how it worked for me:
Source:
windows 10
all firewalls are closed
network access (from windows) to the PC is disabled
external url from gulp 192.168.56.1:3000
proxying local php site from OpenServer
external device - iphone safari/chrome
external (virtual) device - vwware with macos
make sure that Windows Defender firewall monitor in high-risk mode -> rules for incoming connections -> Node.js: Server-side JavaScript is enabled (and other necessary apps)
Solution:
look at what ip address in the home network my PC has (all devices are connected to the same network) - for example 192.168.1.103
in the gulp file I specify it host: "192.168.1.103",
save
checking it out
Important:
for source - external device - iphone safari/chrome - correct url is only 192.168.1.103:3000
for source - external (virtual) device - vwware with macos - correct urls is 192.168.1.103:3000 and 192.168.56.1:3000 both
Visually in pic:
Result:
Checked on all devices, in virtual devices, on the PC itself
browsersync works
the Internet is not lost
there is no address conflict within the network
Hope this will help someone too 🙂
You don't have to change the settings.
run cmd using Administrator
run ipconfig
copy IPv4 address like 192.168.43.52
Now open google on mobile and add http:// at the front and :3000 or :5500 at the back.
like run http://192.168.43.52:3000
Windows 10 x64
WampServer 3.0.6
Everything was working perfect until 01.01.2018
I updated windows and today when i try wamp server not working.
WampIcon -> Right Click -> Tools -> Check state of services:
State of services:
The service 'wampapache64' is NOT started
EXIT error code:1077
Help message for error code 1077 is:
Son açıştan bu yana, hizmeti başlatma denemesi olmadı.
The service 'wampmysqld64' is NOT started
EXIT error code:1077
Help message for error code 1077 is:
Son açıştan bu yana, hizmeti başlatma denemesi olmadı.
The service 'dnscache' is started
WampServer (Apache, PHP and MySQL) will not function properly if any service
'wampapache64'
'wampmysqld64'
'dnscache'
is not started.
searched some google and stackoverflow but no post about "error code 1077"
VC packages for wamp prerequisites were already installed
Don't using IIS or Skype.
port 80 is free
***** Test which uses port 80 *****
===== Tested by command netstat filtered on port 80 =====
Test for TCP
Port 80 is not found associated with TCP protocol
Port 80 is not found associated with TCP protocol
===== Tested by attempting to open a socket on port 80 =====
Your port 80 is not actually used.
Need your ideas what the problem is?
Should i reinstall wampserver???
It sounds like the windows update may have removed the 2 services wampapache64 and wampmysqld64
To get these re-installed is simple.
Using the menus on the Wampmanager icon do this:-
[left click] wampmanager->Apache->Service Administration-> Install Service
and
[left click] wampmanager->MySQL->Service Administration-> Install Service
or if you are using MariaDB then do
[left click] wampmanager->MariaDB->Service Administration-> Install Service
I have just installed Couchbase Server v.3.0.1. Right after intallation, I am redirected to localhost:8091/index.html. The page is blank on Firefox (error 500 in console), Chrome. IE says "cannot view the page" (error 500).
According to suggestion from link I have run:
netstat -a -b -p tcp and get:
...
No information is available about the property
TCP 0.0.0.0:8080 my_host_name:0 LISTENING
[httpd.exe]
TCP 0.0.0.0:8091 my_host_name:0 LISTENING
[ismagent.exe]
...
Installation path without whitespaces:
E:\programy\Couchbase\Server\bin>
Testing server...
> cbworkloadgen.exe -n localhost:8091
error: could not access REST API: localhost:8091/pools/default/buckets; please check source URL, server status, username (-u) and password (-p); exception: ''
Output of netstat shows that imsagent.exe is listening on port 8091. IMS (Intel Services Manager) agent is not Windows core service. Killing that process solved the problem.
My localhost IIS sites recently stopped working and I can't figure out why. If I try and browse to http://localhost after a while I get the error Oops! Google Chrome could not connect to localhost. If I open Fiddler and try again I get a 502 error that states System.Net.Sockets.SocketException A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 127.0.0.1:80
I've tried using netstat -a -b to see if any other applications are blocking port 80, but there doesn't appear to be anything obvious.
I've disabled proxy servers and that doesn't have any affect.
As a last resort I even tried re-installing IIS
Everything has been working fine and I can't think of any configuration changes that would've stopped localhost from working. Any ideas?