My OS is Mac Mountain lion.
My PhpStorm version is 5.0.4.
Here is my php xdebug info:
xdebug.remote_autostart => Off => Off
xdebug.remote_connect_back => Off => Off
xdebug.remote_cookie_expire_time => 3600 => 3600
xdebug.remote_enable => On => On
xdebug.remote_handler => dbgp => dbgp
xdebug.remote_host => 127.0.0.1 => 127.0.0.1
xdebug.remote_log => data/logs/xdebug.log => data/logs/xdebug.log
xdebug.remote_mode => req => req
xdebug.remote_port => 9000 => 9000
xdebug.idekey => no value => no value
I can debug PhpScript Run Type in PhpStorm,It works fine.So I think xdebug configure well.
But after I try follow the "Zero Configure Debug"(Which with Webapplication Run Type),Phpstorm can not connect with the incoming connection.
Here is my step:
Click Start Listion Php Connection.(Toggle the call to green)
Click Run->Break at first line in PhpScript,and set breakpoint at first statement.
Choose My WebApplication Config and click Debug button.Then it launches chrome and link to my phpscript.(with ?XDEBUG_SESSION_START=19869)
In PhpStorm,Debugger shows Waiting for incoming connection with ide key '19869'.
In termial,printlsof -i4TCP:9000.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
webide 288 wangfeng 69u IPv6 0xa83881cdce30c579 0t0 TCP *:cslistener (LISTEN)
Open Chrome's Developer Tool,Select Cookies.
XDEBUG_SESSION 19869 localhost / Wed, 30 Jan 2013 05:27:17 GMT 19
Refresh Chrome.Not able connect with PhpStorm debug connection.
Additional:
My firewall was closed.
My Server is nginx.My phpwebapp and server is all at my local machine.
Does it cause ipv6?
Hopes help!I have try everything,extensions bookmarklets,not work at all.
It's possible that port 9000 is being used by some other process.
In php.ini set xdebug.remote_port=9001 or another unused port of your choosing.
In PHPStorm go to Settings->PHP->Debug and under the Xdebug section set Debug port to 9001.
Restart your web server.
Start debugging.
After checking all the configuration in php.ini file and the IDE, do not forget to add the browser-specific extension that basically communicates via the IDE via IDE Key.
Please refer to this link
Related
I am in a requirement to download multiple files (from a private/internal network) on daily basis.
For which I intended to use selenium with perl to daily download the files from respective locations. I am very new to this domain and need your help.
As a sample program, i am trying to simply connect google.com but it is not getting connected.
my $sel = WWW::Selenium->new( host => "localhost",
port => 80,
browser => "*iexplore",
browser_url => "http://www.google.com",
);
$sel->start;
$sel->open("http://www.google.com");
$sel->type("q", "hello world");
$sel->click("btnG");
$sel->wait_for_page_to_load(5000);
print $sel->get_title;
$sel->stop;
ERROR - > Error requesting http://localhost:4444/selenium-server/driver/:
500 Can't connect to localhost:4444 (Bad address)
i changed the port to 80 and then i get error as:
Error requesting http://localhost:80/selenium-server/driver/:
404 Not Found
Any inputs would be highly appreciated.
I installed Webmin + Virtualmin and made the basic configuration. I created "Server Template" with standard settings and "Account Plan" with standard settings.
After I connected the Virtualmin server to WHMCS, and when I click on the "Login to Control Panel" button, it opens the Virtualmin panel without errors.
In the settings of the hosting products, I selected the Virtualmin module and entered the name Plans and Templates.
Now when a new user orders hosting, it can not be automatically created and gives an error.
In the logs I see this:
Curl Error: 7 - Failed to connect to 185.***.**.41 port 10000: Connection refused
And the query:
Array
(
[program] => create-domain
[domain] =>
[user] =>
[pass] => b5Rcn******
[email] => *****tudio#mail.ru
[template] => Min****host Template
[plan] => P**host Plan
[features-from-plan] =>
)
What could be the problem?
I am creating a project based on WebRTC and Asterisk. I'm forced tu use HTTPS, WSS, SRTP & DTLS, because new browser don't support non-secure connections ... etc
Asterisk 12.8.2
SipJS 0.7.3
Centos 6.7
Chrome 48.0.2
Self-signed certificate (for testing only)
Secure socket used between browser and Asterisk (wss://149.56.XX.XX:8089/ws)
Libsrtp (SRTP) & Pjproject installed
Asterisk server Directly connected to the Internet (Public IP)
Browser is behinf NAT
DTLS-SRTP
WebRTC javascript code located in the same server as Asterisk.
IP's:
Asterisk IP: 149.56.XX.XX
Browser Public IP: 67.212.XX.XX
Browser Local IP: 192.168.0.115
The signaling phase is correct, the peer is well connected to the server.
The aim is to listen to a Playback or Saydigits from Asterisk server. When I run the call, I see that all goes well (SIP and RTP), but no sound in the browser (The volume is up).
I searched on Google, in the forums, but no results .... is that it is a SRTP decryption problem?
Anyone tried this before?
SIP.CONF
[1060]
type=friend
username=1060
host=dynamic
secret=lookrtctest
encryption=yes
avpf=yes
icesupport=yes
context=outgoing
directmedia=no
transport=ws,wss
force_avp=yes
disallow=all
allow=ulaw
allow=alaw
dtlsenable=yes
dtlsverify=fingerprint
dtlscertfile=/etc/asterisk/keys/asterisk.pem
dtlscafile=/etc/asterisk/keys/ca.crt
dtlssetup=actpass
nat=yes,force_rport
Extensions.conf:
[outgoing]
exten => _X.,1,Noop(*** Start Call *** )
exten => _X.,n,Answer()
exten => _X.,n,Playback(vm-from)
exten => _X.,n,SayDigits(123456)
exten => _X.,n,Hangup()
RTP.conf:
[general]
rtpstart=10000
rtpend=20000
icesupport=yes
stunaddr=stun.l.google.com:19302
Http.conf:
[general]
enabled=yes
bindaddr=0.0.0.0
tlsenable=yes
tlsbindaddr=0.0.0.0:8089
tlsprivatekey=/etc/asterisk/keys/asterisk.pem
tlscertfile=/etc/asterisk/keys/asterisk.pem
RTP traces
Sip Traces
Wireshark traces
I'm trying to set up automated testing with PhantomJS, Behat and Sahi on my vagrant machine.
I'm getting the following output, when trying to run a test with behat:
[Behat\SahiClient\Exception\ConnectionException]
Exception has been thrown in "afterStep" hook, defined in FeatureContext::afterStep()
Connection time limit reached
Here is my userdata.properties:
# dirs. Relative paths are relative to userdata dir. Separate directories with semi-colon
scripts.dir=scripts;
# default log directory.
logs.dir=logs
# Directory where auto generated ssl cerificates are stored
certs.dir=certs
# Use external proxy server for http
ext.http.proxy.enable=false
ext.http.proxy.host=
ext.http.proxy.port=
ext.http.proxy.auth.enable=false
ext.http.proxy.auth.name=kamlesh
ext.http.proxy.auth.password=password
# Use external proxy server for https
ext.https.proxy.enable=false
ext.https.proxy.host=
ext.https.proxy.port=
ext.https.proxy.auth.enable=false
ext.https.proxy.auth.name=kamlesh
ext.https.proxy.auth.password=password
# There is only one bypass list for both secure and insecure.
ext.http.both.proxy.bypass_hosts=localhost|127.0.0.1|*.internaldomain.com
# Mark this property true to disable the proxy alert
proxy_alert.disabled=false
And my browswer_types.xml:
<browserTypes>
<browserType>
<name>phantomjs</name>
<displayName>PhantomJS</displayName>
<icon>safari.png</icon>
<path>/usr/bin/phantomjs</path>
<options>--ignore-ssl-errors=yes --proxy=localhost:9999 --ssl-protocol=any /usr/local/sahi/phantomjs-sahi.js</options>
<processName>phantomjs</processName>
<capacity>100</capacity>
<force>true</force>
</browserType>
</browserTypes>
behat.yml:
default:
extensions:
Behat\MinkExtension\Extension:
javascript_session: sahi
browser_name: phantomjs
goutte: ~
sahi:
host: localhost
port: 9999
Sahi run output:
--------
SAHI_HOME: ..
SAHI_USERDATA_DIR: ../userdata
SAHI_EXT_CLASS_PATH:
--------
Sahi properties file = /usr/local/sahi/config/sahi.properties
Sahi user properties file = /usr/local/sahi/userdata/config/userdata.properties
Added shutdown hook.
>>>> Sahi OS v5.0 started. Listening on port: 9999
>>>> Configure your browser to use this server and port as its proxy
>>>> Browse any page and CTRL-ALT-DblClick on the page to bring up the Sahi Controller
-----
Reading browser types from: /usr/local/sahi/userdata/config/browser_types.xml
-----
I've tried reinstalling a bunch of stuff, tried playing around with the ports, processes, proxy settings, nothing.
your vagrant comes with an empty or no db. so when you try to connect to your app, e.g log in with some known user it will crash cause it won't find it!
all the best ;)
Since version 4.3.2 of BrowserType change settings. Since there is no tag force. please check.
https://sahipro.com/docs/using-sahi/sahi-headless-execution-with-phantomjs.html#Documentation since Sahi Pro V4.3.2
I have a rails app that I have deployed to AWS Elastic Beanstalk. The app uses devise to handle user authentication, and its set to be able to invite users.
My issue is that when I try to invite a user, I get the following error:
Net::SMTPFatalError (554 secureserver.net ESMTP No Relay Access Allowed From <my_eb_assigned_ip>
(I am hosting the domain on GoDaddy).
In development, the mailer functionality works fine; my smtp settings are set to (common to all environments):
ActionMailer::Base.delivery_method = :smtp
ActionMailer::Base.smtp_settings = {
:address => "smtpout.secureserver.net",
:port => 80,
:domain => "www.my_domain.com",
:authentication => :plain,
:user_name => "do-not-reply#my_domain.com",
:password => my_pass,
}
And in my production.rb config file:
config.action_mailer.default_url_options = { :host => 'aws_sb.elasticbeanstalk.com' }
Is there another setting I have to enable in Elasticbeanstalk to allow relay access? Or am I missing a production specific setting from my rails configuration?
I figured out it was the port value that I was setting....when I switched the port to 25, it works in production. However, for development, port 25 wasn't working; it would only work in dev when the port was 80.
So I ended up moving the entire smtp mailer settings into the environment specific settings (from the config/environment.rb file), and setting the production port to 25, and the development port to 80, and that appeared to make both environments work.
Edit: After another push, I was seeing the same issue, and none of the ports I tried were resolving the issue. So I ended up switching all my mail functionality to be sent through Amazon SES, and that appears to be functioning great so far.