Hi,

when I’m at home, I have to use a proxy to connect to the internet.
But when I’m connected, I am not able to send any messages. I have to disconnect from my Wifi and send via 3G.
I always get an 404 error.

My iPhone wants to connect to: http://50.56.121.211/deliver

Maybe you could help me, what to do, thanks!

Best regards,
Bastian

Is this for using biteSMS credits?

Yes. biteSMS just says sending failed.
I got this 404 error from my proxy.

When using 3G everythings fine.

Umm, really not sure. Anyone else?

try biteSMS > Settings > About > Reset All. No issues for me.

@MyBro LOL, are you actually running a proxy server?

But the sending address is correct?!

Looks fine.

@Martin – what’s a proxy server..).

It’s a dwarf server, a small one, otherwise known as a poxy server :-)

Okay, thanks for your support. Then I will always disconnect my wifi when sending ;)

Same to my. I’m usinf Squid3+Privoxy. Strange thing because from the logs I see that everything is submitted just perfect but the BiteSMS web server replies with an 404… Doesn’t look like a problem at my side of the line… Please anyone investigate this odd behaviour.

My Privoxy log:
2013-05-19 15:57:37.850 7fdf9588b700 Connect: Listening for new connections …
2013-05-19 15:57:37.850 7fdf94a89700 Connect: Accepted connection from 127.0.0.1 on socket 4
2013-05-19 15:57:37.850 7fdf94a89700 Received: from socket 4: POST http://50.56.121.211/deliver HTTP/1.1\x0d\x0aHost: 50.56.121.211\x0d\x0aAccept: /*\x0d\x0aAccept-Encoding: gzip, deflate\x0d\x0aAccept-Language: de\x0d\x0aContent-Type: text/xml; charset=UTF-8\x0d\x0aPragma: no-cache\x0d\x0aContent-Length: 224\x0d\x0aUser-Agent: biteSMS 7.5 [iPhone Version 6.1.2 (Build 10B146)]\x0d\x0aCache-Control: max-age=259200\x0d\x0aConnection: keep-alive\x0d\x0a\x0d\x0a<?xml version=”1.0” encoding=”UTF-8”?><sms><timestamp>2013-05-19 13:56:19 +0000</timestamp><recipients><to>replaced_for_public_publishing</to></recipients><vouchers><token>replaced_for_public_publishing</token></vouchers><message>test</message></sms>
2013-05-19 15:57:37.852 7fdf94a89700 Connect: Reduced expected bytes to 0 to account for the 224 ones we already got.
2013-05-19 15:57:37.852 7fdf94a89700 Connect: Complete client request received.
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: POST http://50.56.121.211/deliver HTTP/1.1
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Host: 50.56.121.211
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Accept: */
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Accept-Encoding: gzip, deflate
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Accept-Language: de
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Content-Type: text/xml; charset=UTF-8
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Pragma: no-cache
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Content-Length: 224
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: User-Agent: biteSMS 7.5 [iPhone Version 6.1.2 (Build 10B146)]
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Cache-Control: max-age=259200
2013-05-19 15:57:37.852 7fdf94a89700 Header: scan: Connection: keep-alive
2013-05-19 15:57:37.852 7fdf94a89700 Header: Keeping the client header ‘Connection: keep-alive’ around. The server connection will be kept alive if possible.
2013-05-19 15:57:37.852 7fdf94a89700 Header: New HTTP Request-Line: POST /deliver HTTP/1.1
2013-05-19 15:57:37.852 7fdf94a89700 Actions:
2013-05-19 15:57:37.852 7fdf94a89700 Request: 50.56.121.211/deliver
2013-05-19 15:57:37.852 7fdf94a89700 Connect: to 50.56.121.211
2013-05-19 15:57:37.989 7fdf94a89700 Connect: Connected to 50.56.121.211[50.56.121.211]:80.
2013-05-19 15:57:37.989 7fdf94a89700 Connect: Created new connection to 50.56.121.211:80 on socket 5.
2013-05-19 15:57:37.989 7fdf94a89700 Writing: to socket 5: POST /deliver HTTP/1.1\x0d\x0aHost: 50.56.121.211\x0d\x0aAccept: /\x0d\x0aAccept-Encoding: gzip, deflate\x0d\x0aAccept-Language: de\x0d\x0aContent-Type: text/xml; charset=UTF-8\x0d\x0aPragma: no-cache\x0d\x0aContent-Length: 224\x0d\x0aUser-Agent: biteSMS 7.5 [iPhone Version 6.1.2 (Build 10B146)]\x0d\x0aCache-Control: max-age=259200\x0d\x0aConnection: keep-alive\x0d\x0a\x0d\x0a
2013-05-19 15:57:37.990 7fdf94a89700 Writing: to socket 5: <?xml version=”1.0” encoding=”UTF-8”?><sms><timestamp>2013-05-19 13:56:19 +0000</timestamp><recipients><to>replaced_for_public_publishing</to></recipients><vouchers><token>replaced_for_public_publishing</token></vouchers><message>test</message></sms>
2013-05-19 15:57:37.990 7fdf94a89700 Connect: to 50.56.121.211 successful
2013-05-19 15:57:38.164 7fdf94a89700 Received: from socket 5: HTTP/1.1 404 Not Found\x0d\x0aContent-Type: text/html; charset=utf-8\x0d\x0aTransfer-Encoding: chunked\x0d\x0aConnection: keep-alive\x0d\x0aStatus: 404\x0d\x0aCache-Control: no-cache\x0d\x0aContent-Encoding: gzip\x0d\x0a\x0d\x0a450\x0d\x0a…
2013-05-19 15:57:38.165 7fdf94a89700 Header: scan: HTTP/1.1 404 Not Found
2013-05-19 15:57:38.165 7fdf94a89700 Header: scan: Content-Type: text/html; charset=utf-8
2013-05-19 15:57:38.165 7fdf94a89700 Header: scan: Transfer-Encoding: chunked
2013-05-19 15:57:38.165 7fdf94a89700 Header: scan: Connection: keep-alive
2013-05-19 15:57:38.165 7fdf94a89700 Header: scan: Status: 404
2013-05-19 15:57:38.165 7fdf94a89700 Header: scan: Cache-Control: no-cache
2013-05-19 15:57:38.165 7fdf94a89700 Header: scan: Content-Encoding: gzip
2013-05-19 15:57:38.165 7fdf94a89700 Header: Keeping the server header ‘Connection: keep-alive’ around.
2013-05-19 15:57:38.165 7fdf94a89700 Header: Adding: Proxy-Connection: keep-alive
2013-05-19 15:57:38.165 7fdf94a89700 Connect: Looks like we got the last chunk together with the server headers. We better stop reading.
2013-05-19 15:57:38.165 7fdf94a89700 Writing: to socket 4: HTTP/1.1 404 Not Found\x0d\x0aContent-Type: text/html; charset=utf-8\x0d\x0aTransfer-Encoding: chunked\x0d\x0aConnection: keep-alive\x0d\x0aStatus: 404\x0d\x0aCache-Control: no-cache\x0d\x0aContent-Encoding: gzip\x0d\x0aProxy-Connection: keep-alive\x0d\x0a\x0d\x0a
2013-05-19 15:57:38.165 7fdf94a89700 Writing: to socket 4: 450\x0d\x0a…
2013-05-19 15:57:38.166 7fdf94a89700 Connect: Done reading from server. Content length: 1116 as expected. Bytes most recently read: 1116.
2013-05-19 15:57:38.166 7fdf94a89700 Connect: Tainting client socket 4 due to unread data.
2013-05-19 15:57:38.166 7fdf94a89700 Connect: Closing server socket 5 connected to 50.56.121.211. Keep-alive: 1. Tainted: 1. Socket alive: 1. Timeout: 300. Configuration file change detected: 0
2013-05-19 15:57:38.166 7fdf94a89700 Connect: Closing client socket 4. Keep-alive: 1. Socket alive: 1. Data available: 0. Configuration file change detected: 0. Requests received: 1.