Anyone working with Intalio|BPMS?
I'm trying to implement a process using the Comunity Edition, and I'm having a problem I can't seem to solve.
The process has an AJAX Form and if I go to ui-fw in the server using localhost everything works, but if I try to access the server remotely using the url it doesn't.
The iframe for the AJAX Form is pointing to localhost and not the url.
From the very bad foruns at Intalio, I've checked /tried:
deploy from the designer using the url
finding every mention of localhost in the process deploy dir, and also in the var/conf
Still no luck.
Any ideas anyone??
Thanks in advance
Ricardo, IIRC the form is deployed according to the settings you use in the deployment manifest. I believe you can also set an other host name in the deployment manifest to deploy to localhost, but declare a different host name for the form and processes.
Related
Following the doc from Rundeck, however the only button I have under "Sources tab" is "ResourceModelSource"
When I click that button I get a blank
PPS Issue happened on previous version - new to RunDeck, so I can't say that it EVER worked
I tried adding a manual resouces.xml in the project director y(Which I had to manually create, which tells me that's another issue) and reloading RD but that did not seem to work
While it's not the likely cause, I'll mention it here incase it IS relevant, I'm hosting on port 4440 however I'm using nginx to forward http (not https) requests on 443 to 4440, this is due to corp net sec policy.
I'm sure it's something where it's having an i/o issue on the local host, however I'm not seeing anything in the logs.
That is a known issue when you have Rundeck installed behind a proxy server, take a look at this: https://github.com/rundeck/rundeck/issues/6278 the solution is to set the grails.ServerURL (rundeck-config.properties file) with the exit URL defined for Rundeck in your proxy server (e.g: grails.serverURL=http://my_domain/rundeck), then restart the Rundeck service.
I’m from Taiwan and not good at English, but I’ll try my best to explain my question.
I use Netlify CMS to build my Hugo website.
Everything runs well, but when I want to change and check if the CMS’s configuration and style is okay, I always need to push my repository to Github, which is disturb me a lot.
So I tried to use local_backend: true in admin/config.yml, then used this command: npx netlify-cms-proxy-server.
then the window showed:
info: Netlify CMS File System Proxy Server configured with C:\Users\june.wu\Documents\GitHub\house-blog-hugo-cms
info: Netlify CMS Proxy Server listening on port 8081
It looked it ran successfully on localhost:8081.
But when I type localhost:8081 in browser it showed: Cannot GET /
How can I solve this problem?
I can confirm what said in the previous answer. Run npx netlify-cms-proxy-server and go to localhost:8080/admin or try also localhost:8080/admin/ (with ending slash). It should work if you are using default 8080 port.
Ignore that CMS is on port 8081 as said in the script log
for anyone looking at this in and still finding it unclear, as said in the docs you need to go to your regular development server based on the SSG (static site generator) that you are using once you have started both the NetlifyCMS and SSG dev servers. See point 5 in the beta features docs here.
You are not supposed to try visit the NetlifyCMS 8081 default port to use the CMS locally.
I have also seen behaviour mentioned by a few people that it only works with a / at the end of the path. So for example if using Astro as your SSG (which uses the port :3000 for it's dev server) you should try both:
http://localhost:3000/admin/
http://localhost:3000/admin
Although I have been having issues with the NeltlifyCMS dev server with Astro still...
I am trying to configure or setup the production environment of whatsapp business api as mentioned in the link https://developers.facebook.com/docs/whatsapp/installation/prod-single-instance
I have done everything mentioned in this my dockers are also running on port:9090 as can be seen in the image
still I can't access it. Whenever I try to call https://localhost:9090 the error with "This site can’t be reached" occurs. Whatsapp business api does not have good documentation or tutorials till now. So this site is the only last way for me.
I had a similar problem which could be your case, I saw the docker containers OK but nothing was working. After a day searching I saw where it happened, my problem was I installed mysql MANUALLY (not docker container) in the same instance where docker is running and in db.env I just used 127.0.0.1, this was passed literally to docker container, then looking at a the wait_on_mysql.sh script, the whastapp docker containers were waiting util the mysql ip has conectivity to actually do something and was printing "MySQL is not up yet - sleeping" each second, of course they wouldn't find any conectivity.
Since my instalation is for development, and I am already using such database to other stuff, my solution was to use the 172.17.0.1(docker gateway of the containers) IP instead, then add two sets of network iptables rules to the host to redirect from the docker containers IP to the IP binded by mysql when using such port (3306, the default in my case). After that everything works well. I think there are better solutions, but I didn't want to go far on it, you should evaluate you case if apply.
check the command:
docker-compose logs > debug_output.txt
That gives you insight about whats happening, hope it can helps someone.
I think your setup is already complete. You just need to start with the registration process and start sending messages. The containers are up and running but calling https://localhost:9090 won't send you any response as this is not any specified API endpoint expected to be used.
Since you're using prod single instance, the documentation can be found here which seems pretty straight forward. https://developers.facebook.com/docs/whatsapp/installation/prod-single-instance
You seem to have completed till the 7 steps. The next step can be to perform a health check to make sure it is healthy. The API endpoint for that would be https://localhost:9090/v1/health https://developers.facebook.com/docs/whatsapp/api/health
Has your db also been setup?
I cannot see it in the docker screenshot.
Also - you have to accept the certificate, as it does not have a public CA issues certificate.
I am trying to connect to an external SOAP service using PHP and have written a small php test script that just connects to the service and performs a simple request to check everything is working.
This all works correctly but when I run via a browser request, it is very slow taking somewhere in the region of 40s to establish the initial connection. When I do the same request using the exact same script on the command line, it goes through straight away.
Does anyone have any ideas as to why this might be?
Cheers
PHP caches the wsdl in /tmp. If you run from the command line first, the cache file will be owned by whatever user you're running the script as, and apache won't be able to read the cache. The wsdl will have to be downloaded and parsed every time which will be slow.
Check the permissions of /tmp/wsdl*.
Maybe external SOAP service trying to check your IP, and your server has ICMP allowed, when your local network - not.
Anyway, this question might be answered more clearly by administrator of external SOAP service :)
Is there a difference between the php.inis that are being used?
On a standard ubuntu server installation:
diff /etc/php5/apache2/php.ini /etc/php5/cli/php.ini
//edit:
Another difference might be in the include paths. Had this trouble myself on a local test server, it didn't actually use the soap class that was included (it didn't include anything, because the search paths weren't valid), but it included the built-in soap_client class.
i created a web service, upload it to my site on a remote server.
i tried to browse it but i cant, i also tried to add web reference to his adress through vs08 but the same problem happened there.
Ok, based on your comment:
i didnt get any errors, only when
beowsing it i get a 404 page not found
error, the name space is
"http://www.poppetz.com/poppetz"; but
the service is actually in
http://www.popetz.co.il/Services/Poppetz.asmx
maybe this is the problem??? i
deployed it with vs08 through ftp –
Chen Kinnrot (2 mins ago)
The namespace of your service will have nothing to do with you being able to access it.
If you put a plain old test.html that echo "hello world" back to you and put that in the same directory as your service, can you access that?
ie: http://www.popetz.co.il/Services/test.html
Can you get access to the machine hosting the web services. If so, if you look in the IIS manager, can you see the ASMX in the web site you are expecting it be in?
If not, then start looking at the IIS configuration and make sure that web site directory is the same folder as you are dumping the web service files.
10x everyone, the server provider change some iis config and everything works...\