I think I might have identified my problem. I was testing on a windows machine, making use of WSL2. When I tried building the container using our CI/CD pipeline, texis installs properly.
So I don't know what the issue was, but I think it was unrelated to either texis or centos.
Search found 39 matches
- Mon May 19, 2025 6:16 pm
- Forum: Texis Webscript (Vortex)
- Topic: Docker build fails - texis 7.07
- Replies: 2
- Views: 50321
- Mon May 19, 2025 5:19 pm
- Forum: Texis Webscript (Vortex)
- Topic: Docker build fails - texis 7.07
- Replies: 2
- Views: 50321
Docker build fails - texis 7.07
I'm trying to build a docker container which uses docker 7.07.1591052018. For the base OS, I have been using centOS. I am finding that on both centOS 6 & 7, when I run the install, the installer seems to hang on this command, which appears to launch vhttpd
"$BinDir/vhttpd" -d "$ServerRoot"
I tried omitting this line from the installer, and the install completes. But when I do this, vortex scripts do not execute correctly. If I try to manually run vhttpd after the install, the command hangs forever.
My preference is to get this working on centos 6/7, as this matches prod machines. For the sake of experimenting, I also tried installing on centos 8. On centOS 8, the install completes, but texis still does not function correctly. A simply fetch command will timeout. I am able to run a ping from the machine to the target domain, and reach it so I don't think it is a connectivity issue.
I have also tested by downgrading to texis 7.06, and that installs and runs properly. So I seem to be at an impasse with how to get 7.07 to install via dockerfile. Are there any known issues with texis 7.07 and centos, or with docker?
"$BinDir/vhttpd" -d "$ServerRoot"
I tried omitting this line from the installer, and the install completes. But when I do this, vortex scripts do not execute correctly. If I try to manually run vhttpd after the install, the command hangs forever.
My preference is to get this working on centos 6/7, as this matches prod machines. For the sake of experimenting, I also tried installing on centos 8. On centOS 8, the install completes, but texis still does not function correctly. A simply fetch command will timeout. I am able to run a ping from the machine to the target domain, and reach it so I don't think it is a connectivity issue.
I have also tested by downgrading to texis 7.06, and that installs and runs properly. So I seem to be at an impasse with how to get 7.07 to install via dockerfile. Are there any known issues with texis 7.07 and centos, or with docker?
- Mon Dec 23, 2024 10:08 am
- Forum: Texis Webscript (Vortex)
- Topic: POST returning 404
- Replies: 3
- Views: 13967
Re: POST returning 404
There are no errors in vortex.log. The site simply responds with a 404 errors page.
My initial thought was my POST request is not correct, but I have gone over it a number of times and am fairly sure it is fine. I have a 3rd party tool which I can access which takes my simple request and simulates the handshaking done in a browser. When using that service, I get the proper response. So I am fairly confident the issue isn't with the POST request being incorrect, which is why I was looking into other issues, such as the vortex engine being too outdated for this server. But I don't know how to detect whether that is the case here.
My initial thought was my POST request is not correct, but I have gone over it a number of times and am fairly sure it is fine. I have a 3rd party tool which I can access which takes my simple request and simulates the handshaking done in a browser. When using that service, I get the proper response. So I am fairly confident the issue isn't with the POST request being incorrect, which is why I was looking into other issues, such as the vortex engine being too outdated for this server. But I don't know how to detect whether that is the case here.
- Fri Dec 20, 2024 6:00 pm
- Forum: Texis Webscript (Vortex)
- Topic: POST returning 404
- Replies: 3
- Views: 13967
POST returning 404
I have a simple POST request that I am trying to make, but it seems to constantly fail in Vortex. I am able to get a response just fine using both cURL and Postman, so I don't believe it is an issue of server-side blocking.
Sample Vortex code is listed below
cURL request is also listed, which consistently gets a proper response.
I am using Commercial Version 7.07.1591132145 20200602 (x86_64-unknown-winnt-64-64). Is there possibly some low level handshaking that is failing with this older Vortex version when communicating with this server?
Sample Vortex code is listed below
Code: Select all
<urlcp header "Host" "www.amazon.com">
<urlcp header "Accept" "text/html,*/*">
<urlcp header "Accept-Language" "en-US,en;q=0.5">
<urlcp header "Accept-Encoding" "gzip, deflate, br">
<urlcp header "Origin" 'https://www.amazon.com'>
<urlcp header "Connection" "keep-alive">
<urlcp header "Referer" https://www.amazon.com/gp/product/B0D5JLH3RJ>
<urlcp header "Sec-Fetch-Dest" "empty">
<urlcp header "Sec-Fetch-Mode" "cors">
<urlcp header "Sec-Fetch-Site" "same-origin">
<urlcp header "TE" "trailers">
<urlcp header "Content-Type" "application/x-www-form-urlencoded;charset=UTF-8">
<urlcp header "X-Requested-With" "XMLHttpRequest">
<$submiturl='https://www.amazon.com/hz/reviews-render/ajax/medley-filtered-reviews/get/ref=cm_cr_dp_d_fltrs_srt'>
<$submitdata='language=en_US&asin=B0D5JLH3RJ&sortBy=recent&scope=reviewsAjax1'>
<urlcp useragent "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0">
<submit URL=$submiturl method=POST DATA=$submitdata CONTENT-TYPE='application/x-www-form-urlencoded;charset=UTF-8'>
Code: Select all
curl 'https://www.amazon.com/hz/reviews-render/ajax/medley-filtered-reviews/get/ref=cm_cr_dp_d_fltrs_srt' --compressed -X POST -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0' -H 'Accept: text/html,*/*' -H 'Accept-Language: en-US,en;q=0.5' -H 'Accept-Encoding: gzip, deflate, br' -H 'X-Requested-With: XMLHttpRequest' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -H 'Origin: https://www.amazon.com' -H 'Connection: keep-alive' -H 'Referer: https://www.amazon.com/gp/product/B0D5JLH3RJ' -H 'Sec-Fetch-Dest: empty' -H 'Sec-Fetch-Mode: cors' -H 'Sec-Fetch-Site: same-origin' -H 'TE: trailers' --data-raw 'language=en_US&asin=B0D5JLH3RJ&sortBy=recent&scope=reviewsAjax1'
- Wed Dec 20, 2017 5:56 pm
- Forum: Texis Webscript (Vortex)
- Topic: I/O error
- Replies: 5
- Views: 22468
I/O error
I was eventually able to reliably fetch the page. The site appears to be very particular about what headers and user agent is being passed. It appears HTTP/2.0 was not the issue here.
- Wed Dec 20, 2017 3:22 pm
- Forum: Texis Webscript (Vortex)
- Topic: I/O error
- Replies: 5
- Views: 22468
I/O error
I should probably also mention that I am using version 7.03.1434496242 20150616 (x86_64-unknown-winnt-64-64)
- Wed Dec 20, 2017 3:21 pm
- Forum: Texis Webscript (Vortex)
- Topic: I/O error
- Replies: 5
- Views: 22468
I/O error
I've recently been revisiting this issue and am wondering if this site using HTTP/2.0 is causing an issue. Is Vortex capable of handling sites using HTTP/2.0?
A sample URL that is failing would be https://www.zomato.com/ncr/bukhara-itc- ... hi/reviews. I can load this page in my browser and I find that I can reproduce the request in curl when the following parameters are set --2.0 and --compressed.
A sample URL that is failing would be https://www.zomato.com/ncr/bukhara-itc- ... hi/reviews. I can load this page in my browser and I find that I can reproduce the request in curl when the following parameters are set --2.0 and --compressed.
- Thu Feb 02, 2017 12:43 pm
- Forum: Texis Webscript (Vortex)
- Topic: I/O error
- Replies: 5
- Views: 22468
I/O error
I've been running into an error that I can't quite figure out. When fetching https://www.zomato.com/, the fetch fails with the following message...
I/O error: An established connection was aborted by the software in your host machine in the function htbuf_readnblk
The script ultimately reports it as an SSL error. Note that this was done using Texis 6. I am aware that there was some new features added with v7 related to SSL so I also tried the same fetch on a Texis 7 machine. That fetch also fails although with a different error...
Timeout reading data from www.zomato.com:443 in the function htbuf_readnblk
This one ends up being reported as a connection timeout.
The unexpected observation I ended up making was that these errors only seem to occur when I set a typical browser as the user agent. Leaving the user agent blank results in the fetch succeeding on either version of Texis.
Is there a configuration I am missing as to why the fetches fail when a browser agent is set or is this simply a problem with the site I am fetching?
I/O error: An established connection was aborted by the software in your host machine in the function htbuf_readnblk
The script ultimately reports it as an SSL error. Note that this was done using Texis 6. I am aware that there was some new features added with v7 related to SSL so I also tried the same fetch on a Texis 7 machine. That fetch also fails although with a different error...
Timeout reading data from www.zomato.com:443 in the function htbuf_readnblk
This one ends up being reported as a connection timeout.
The unexpected observation I ended up making was that these errors only seem to occur when I set a typical browser as the user agent. Leaving the user agent blank results in the fetch succeeding on either version of Texis.
Is there a configuration I am missing as to why the fetches fail when a browser agent is set or is this simply a problem with the site I am fetching?
- Wed Aug 17, 2016 4:53 pm
- Forum: Texis Webscript (Vortex)
- Topic: Page size
- Replies: 1
- Views: 18360
Page size
Does urlinfo report the transferred page size from a page fetch? I've found I can sometimes get this by analyzing the headers but not all sites are sending a Content-Length header.
- Mon Mar 09, 2015 1:14 pm
- Forum: Texis Webscript (Vortex)
- Topic: SSL handshake failure
- Replies: 2
- Views: 2813
SSL handshake failure
I've been trying to do a fetch of this page...
https://de.trustpilot.com/categories/other
I continue to run into this error...
123: Cannot complete SSL handshake with de.trustpilot.com:443: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
Other SSL sites seem to fetch fine. Am I missing a setting to get this one to work?
https://de.trustpilot.com/categories/other
I continue to run into this error...
123: Cannot complete SSL handshake with de.trustpilot.com:443: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
Other SSL sites seem to fetch fine. Am I missing a setting to get this one to work?