Fatal error: Call to undefined function apc_fetch() in /var/www/html/sgs/bin/core/functions.php on line 1842

Massimo Arnaudo

unread,

Feb 21, 2021, 6:31:04 AM2/21/21

to simple-g...@googlegroups.com

Hello,

I had to move the program to another instance of AWS, but I'm blocked by the error message in the subject of the email.
I tried to install the extension, but without success:

[ec2-user @ ip-10-0-0-38 share] $ sudo yum install php-pecl-apc
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core | 3.7 kB 00:00:00
No package php-pecl-apc available.
Error: Nothing to do

I also installed the following, but it didn't change the error message:

Installed:
php-pecl-memcache.x86_64 0: 3.0.8-4.amzn2

Dependency Installed:
libxslt.x86_64 0: 1.1.28-6.amzn2 php-pear.noarch 1: 1.10.12-5.amzn2 php-process.x86_64 0: 5.4.16-46.amzn2.0.2 php-xml.x86_64 0: 5.4 .16-46.amzn2.0.2

Complete!
[ec2-user @ ip-10-0-0-38 /] $ sudo systemctl stop httpd
[ec2-user @ ip-10-0-0-38 /] $ sudo systemctl start httpd

How can I solve?

Thank you
Massimo

Patrick Pliessnig

unread,

Feb 22, 2021, 3:45:03 AM2/22/21

to Simple Groupware

Hello Massimo

There are a few things you could consider.

First you might have a version mismatch for your aws instance. The command 'sudo yum install php-pecl-apc' should work with aws php sdk version 2 for php5.3. So please try to ensure that your particular instance uses these versions. If you use another sdk, then there might be another command to install php apc.

If your versions are correct, there might be a technical problem of your aws instance. In this case consider getting help directly from an aws support team.

Last but not least, just disable APC in your SGS instance for session caching. Go to your settings page, there you will find the option for APC Session Cache. Simply uncheck it and those APC functions shouldn't be called anymore.

Cheers

Patrick

Massimo Arnaudo

unread,

Feb 24, 2021, 6:23:08 AM2/24/21

to simple-g...@googlegroups.com

Hello Patrick,

the php version is different:

[ec2-user@ip-10-0-0-38 ~]$ sudo yum install php-pecl-apc

Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core | 3.7 kB 00:00

No package php-pecl-apc available.
Error: Nothing to do

[ec2-user@ip-10-0-0-38 ~]$ php -v
PHP 5.4.16 (cli) (built: Oct 31 2019 18:34:05)
Copyright (c) 1997-2013 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies

So, if i understand correctly, i have to use another command?

Can you explain how?

Thanks

Massimo

--
You received this message because you are subscribed to the Google Groups "Simple Groupware" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simple-groupwa...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simple-groupware/2588c8c4-a343-4fae-b30e-69831a6d25e4n%40googlegroups.com.

Patrick Pliessnig

unread,

Feb 25, 2021, 7:53:29 AM2/25/21

to Simple Groupware

Hello Massimo

The exact command depends on the version of the AWS SDK for PHP you are using.

My suggestion is to try this command here: yum install php54-pecl-apc

I also suggest you make a snapshot of your server before you do this. This way you can roll back if anything goes wrong.

See here for more info:

https://docs.aws.amazon.com/aws-sdk-php/v2/guide/performance.html#installing-on-amazon-linux

Massimo Arnaudo

unread,

Feb 25, 2021, 12:19:13 PM2/25/21

to simple-g...@googlegroups.com

Hi Patrick,
unfortunately the package that you indicate and that indicates the manuals you suggested does not exist and I have not even found the documentation that suggests an upgrade to at least PHP 5.5.

I don't understand why the instance I started no more than a week ago has such an outdated version of PHP ...

Fortunately I had taken the snapshot, and I'll probably go back; this choice to upgrade to the Amazon Linux 2 AMI version was dictated by the fact that the tt-rss program (https://tt-rss.org/) that needs PHP 7 to work no longer works.
SGS doesn't work with PHP 7 and so I had to have both versions.
As a consequence I was trying to install two Apaches, one with php 5 and another with php 7 (https://marstefo.ovh/2017/installare-php-5-6-e-php-7-in-contemporanea-con-apache -2/).
But to use the command systemctl AMI2 is necessary and hence the choice to change the instance ...

A greeting
Maximum

To view this discussion on the web visit https://groups.google.com/d/msgid/simple-groupware/d1d3ffe3-cdd5-4044-9615-309bbad87e99n%40googlegroups.com.

Patrick Pliessnig

unread,

Feb 26, 2021, 4:01:47 AM2/26/21

to Simple Groupware

Massimo

Have you considered to run tt-rss as a docker image [1]?

There seem to be prebuild docker images out-of-the-box [2,3].

Maybe you could run them directly on your old linux AMI or on another docker instance.

[1] https://docs.aws.amazon.com/AmazonECS/latest/developerguide/docker-basics.html

[2] https://tt-rss.org/wiki/InstallationNotes

[3] https://hub.docker.com/u/cthulhoo

Massimo Arnaudo

unread,

Feb 27, 2021, 9:25:43 AM2/27/21

to simple-g...@googlegroups.com

Hi Patrick,

I read the pages you suggested in the three links, but I must admit that it is not very clear to me ...

Premise

yesterday I went back from the old backup / snapshot, so SGS works but TT-RSS doesn't (Fatal Error: PHP version 7.0.0 or newer required. You're using 5.6.40)

Development (still to be done)
Keeping the current instance, I follow the instructions to first install the docker engine and then the specific ttrss-docker.

Questions
1) PHP7 do I have to install it or is it already present in the ttrss-docker?
2) Is Apache also in ttrss-docker and does it work in parallel with Apache already in use?
3) And the MySQL database?

Thank you

Massimo

To view this discussion on the web visit https://groups.google.com/d/msgid/simple-groupware/d794a1da-e951-40df-acb8-88339b11a9efn%40googlegroups.com.

Patrick Pliessnig

unread,

Mar 4, 2021, 9:27:31 AM3/4/21

to Simple Groupware

Hi Massimo

Docker is a system where you can:

1) build so called images from applications

2) create a container from an image

3) configure this container and

4) execute this container to run the application.

This application in the container then runs isolated from the rest on your linux OS.

Luckily other people create images for you, so you can simply download such an image, create a container, configure it and run it.

In the case of ttrss other people created images where they put together a webserver, php and the application ttrss. Usually they don't use Apache but Ngnix. But don't worry, it's all packed together in the image and isolated from the rest. So it can be executed without interference with the rest of your linux.

I tested the whole with an image that you can download from https://hub.docker.com/r/ginkel/ttrss. Once you have downloaded the image, you need to configure the container according to the instructions on this link (the reason I changed is that with this image, the maintainer gives instructions for configuration).

Most importantly you need to configure the database you want to use. Probably this is mySQL on your linux. So, lets do it:

Probably in your case the instructions are like this:

Install the docker engine (please refer also to the aws instructions):

sudo yum install docker

Start it as a service:

sudo service docker start

Get the image (maybe it will ask for login data to hub.docker.com):

docker pull ginkel/ttrss

Start the container by passing the configuration parameters. This will be something like this if you use your normal Apache mySQL, but check the ginkel/ttrss for instructions:

docker run -d -e DB_HOST=your-host-IP -e DB_PORT=3306 DB_NAME=your-name DB_USER=your-user DB_PASS=your-password -p 80:80 ginkel/ttrss

I hope this helps

Patrick

Massimo Arnaudo

unread,

Mar 4, 2021, 12:02:24 PM3/4/21

to simple-g...@googlegroups.com

Hi Patrick,

your clarifications are always simple, complete and exhaustive.

Now i can use my old database, so i have typed the string:

[ec2-user@ip-10-0-0-70 ~]$ sudo service mysqld start
Starting mysqld: [ OK ]

[ec2-user@ip-10-0-0-70 ~]$ docker run -d -e DB_HOST=localhost -e DB_PORT=3306 -e DB_NAME=<mydbname> -e DB_USER=<mydbuser> DB_PASS=<mydbpassword> -p 80:80 ginkel/ttrss
docker: invalid reference format: repository name must be lowercase.

Hmmm, but the repository is in lowercase..

Any suggestions?

Thanks

Massimo

To view this discussion on the web visit https://groups.google.com/d/msgid/simple-groupware/bca93e1b-9c99-420e-85ba-af0916c5aea0n%40googlegroups.com.

Patrick Pliessnig

unread,

Mar 5, 2021, 3:01:46 AM3/5/21

to Simple Groupware

From the point of view of a docker image, anything else could be a repository.

First it makes sense to know some docker command to work with images and containers [1,2]

Second, in your command, replace localhost with the ip-address (or the domain) of you linux instance. The reason is that from the point of view of your container your linux instance is another computer. So localhost points to the container itself.

Cheer Patrick

[1] https://www.tutorialspoint.com/docker/docker_images.htm

[2] https://www.tutorialspoint.com/docker/docker_containers.htm

Massimo Arnaudo

unread,

Mar 6, 2021, 10:04:04 AM3/6/21

to simple-g...@googlegroups.com

Hi Patrick,

thanks per documentation.

I solved the previous problem, a -e was missing in front of DB_PASS ...
I also found port 80 busy, so I provided 8080

[ec2-user@ip-10-0-0-70 tt-rss]$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
ginkel/ttrss latest d2769464cecd 2 years ago 190MB

[ec2-user@ip-10-0-0-70 tt-rss]$ docker run -d <run like a daemon>

-e DB_HOST=10.0.0.70 <myprivate DNS, where is the database >

-e DB_PORT=3306

-e DB_NAME=<my database name>

-e DB_USER=<my database username>

-e DB_PASS=<my database password>

-e DB_TYPE=mysql <the database type>

-e SELF_URL_PATH=http://3.65.53.160/ttrss <where i can find the feed reader>

-p 8080:80 <the port, because the 80 is occupied by Apache>

ginkel/ttrss <the image name>

845446b9ca54a7d411ecdf6ff553ecb093a096bc80a59794c226f87a9ea8ab83

[ec2-user@ip-10-0-0-70 tt-rss]$ docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

[ec2-user@ip-10-0-0-70 tt-rss]

Why i can not find anythings?

So i tried without the damon flag:

[ec2-user@ip-10-0-0-70 tt-rss]$ sudo service mysqld start
Starting mysqld: [ OK ]
[ec2-user@ip-10-0-0-70 tt-rss]$ docker run -e DB_HOST=10.0.0.70 -e DB_PORT=3306 -e DB_NAME=<dbname> -e DB_USER=<db user> -e DB_PASS=<db pwd> -e DB_TYPE=mysql -e SELF_URL_PATH=http://3.65.53.160/ttrss -p 8080:80 ginkel/ttrss
Failed to connect to mysql:host=10.0.0.70;port=3306;dbname=<dbname>; (user = <dbuser>, pw = <db pwd>)
Database login failed, trying to create...
Failed to connect to mysql:host=10.0.0.70;port=3306; (user = <db user>, pw = <db pwd>)
PHP Fatal error: Uncaught PDOException: SQLSTATE[HY000] [1045] Access denied for user '<db user>'@'ip-172-17-0-2.eu-central-1.compute.internal' (using password: YES) in /configure-db.php:137
Stack trace:
#0 /configure-db.php(137): PDO->__construct('mysql:host=10.0...', '<db user>', '<db pwd>')
#1 /configure-db.php(68): dbconnect(Array)
#2 {main}
thrown in /configure-db.php on line 137

so i view the mysql server status:

mysql> \s
--------------
mysql Ver 14.14 Distrib 5.5.62, for Linux (x86_64) using readline 5.1

Connection id: 4
Current database:
Current user: <db name>@localhost
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server version: 5.5.62 MySQL Community Server (GPL)
Protocol version: 10
Connection: Localhost via UNIX socket
Server characterset: latin1
Db characterset: latin1
Client characterset: utf8
Conn. characterset: utf8
UNIX socket: /var/lib/mysql/mysql.sock
Uptime: 8 min 54 sec

Threads: 1 Questions: 7 Slow queries: 0 Opens: 33 Flush tables: 1 Open tables: 26 Queries per second avg: 0.013
--------------

mysql>

Now i have changed the IP connecton for MySQL:

mysql> GRANT ALL ON <db name>.* TO '<db user>'@'10.0.0.70' IDENTIFIED BY '<db user password>';

retyped the command:

[ec2-user@ip-10-0-0-70 tt-rss]$ docker run -e DB_HOST=10.0.0.70 -e DB_PORT=3306 -e DB_NAME=<db name> -e DB_USER=<db user> -e DB_PASS=<db pwd> -e DB_TYPE=mysql -e SELF_URL_PATH=http://3.65.53.160/ttrss -p 8080:80 ginkel/ttrss Failed to connect to mysql:host=10.0.0.70;port=3306;dbname=<db name>; (user = <db user>, pw = <db pwd>)
Failed to connect to mysql:host=10.0.0.70;port=3306;dbname=<db name>; (user = <db user>, pw = <db pwd>)
/var/tmp
2021-03-06 14:52:54,951 CRIT Supervisor running as root (no user in config file)
2021-03-06 14:52:54,951 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf.d/ttrss-update-daemon.conf" during parsing
2021-03-06 14:52:54,952 INFO supervisord started with pid 1
2021-03-06 14:52:55,955 INFO spawned: 'nginx' with pid 10
2021-03-06 14:52:55,956 INFO spawned: 'php-fpm' with pid 11
2021-03-06 14:52:55,957 INFO spawned: 'ttrss-update-daemon' with pid 12
[14:52:56/12] Spawn interval: 120 sec
Schema version is wrong, please upgrade the database. [so the database is running and it is connected?]
2021-03-06 14:52:56,042 INFO exited: ttrss-update-daemon (exit status 0; not expected)
[06-Mar-2021 14:52:56] NOTICE: fpm is running, pid 11
[06-Mar-2021 14:52:56] NOTICE: ready to handle connections
[06-Mar-2021 14:52:56] NOTICE: systemd monitor interval set to 10000ms
2021-03-06 14:52:57,055 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-03-06 14:52:57,056 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-03-06 14:52:57,057 INFO spawned: 'ttrss-update-daemon' with pid 16
[14:52:57/16] Spawn interval: 120 sec
Schema version is wrong, please upgrade the database.
2021-03-06 14:52:57,094 INFO exited: ttrss-update-daemon (exit status 0; not expected)
2021-03-06 14:52:59,097 INFO spawned: 'ttrss-update-daemon' with pid 17
[14:52:59/17] Spawn interval: 120 sec
Schema version is wrong, please upgrade the database.
2021-03-06 14:52:59,133 INFO exited: ttrss-update-daemon (exit status 0; not expected)
2021-03-06 14:53:02,138 INFO spawned: 'ttrss-update-daemon' with pid 18
[14:53:02/18] Spawn interval: 120 sec
Schema version is wrong, please upgrade the database.
2021-03-06 14:53:02,175 INFO exited: ttrss-update-daemon (exit status 0; not expected)
2021-03-06 14:53:03,177 INFO gave up: ttrss-update-daemon entered FATAL state, too many start retries too quickly

So, where coud be the error?

Thnaks

Massimo

To view this discussion on the web visit https://groups.google.com/d/msgid/simple-groupware/de3f0c91-959e-4518-bec5-038f1f35a849n%40googlegroups.com.

Patrick Pliessnig

unread,

Mar 7, 2021, 6:10:27 AM3/7/21

to Simple Groupware

Hi Massimo

My guess 1 is you are close:

try running docker as sudo. like: sudo docker container ls --all

My guess 2 is:

The error message: "Schema version is wrong, please upgrade the database" is a ttrss error message (which means you are technically connected to the db).

The ginkel/ttrss is newer than what you have on your linux and it cannot connect with your normal db-user because the db has an outdated db-schema.

So you need to start the container with the db super user that has the privilege to upgrade the db-schema.

See ( https://hub.docker.com/r/ginkel/ttrss )

the parameters to search for are:

-e DB_ENV_USER=<your user>

-e DB_ENV_PASS=<your pw>

(maybe you need to call your ttrss url to execute, maybe it executes automatically)

(maybe backup your db before doing this, just in case)

Cheers

Patrick

Massimo Arnaudo

unread,

Mar 7, 2021, 1:21:53 PM3/7/21

to simple-g...@googlegroups.com

Hi Patrick,

Guess 1:

[ec2-user@ip-10-0-0-70 ~]$ sudo docker container ls --all

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

1857a48e8e8b ginkel/ttrss "/entrypoint.sh" 27 hours ago Up 27 hours 0.0.0.0:8080->80/tcp vibrant_shtern
74eedab86452 ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (255) 27 hours ago adoring_bardeen
08a592a519ab ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (0) 27 hours ago practical_saha
95297f64b9b4 ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (0) 27 hours ago blissful_ptolemy
2bf61371f0a2 ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (255) 27 hours ago lucid_brown
82fd0ae7afcc ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (255) 27 hours ago compassionate_ellis
be0e9393d712 ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (255) 27 hours ago naughty_wilson
57379ec869aa ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago nervous_margulis
337679505ece ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago suspicious_wescoff
b660374ea152 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago wonderful_kare
f4be7443a86d ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago pensive_margulis
997a0c96f875 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (1) 28 hours ago beautiful_cerf
45320e7ba728 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (1) 28 hours ago wonderful_bhabha
845446b9ca54 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago amazing_shtern
2d0d17a260f7 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago xenodochial_jackson
bfb3605376d6 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago nostalgic_curie
1f2e298e30b4 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (137) 28 hours ago quirky_mendel
8e31a5576926 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago festive_bohr
e2a7dccbdc4f ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago gracious_snyder
f4a7a31f0fab ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago goofy_swirles
dab2b501192d ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 28 hours ago trusting_davinci
1ef3f4def609 ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 29 hours ago jolly_payne
d55f7062bb3d ginkel/ttrss "/entrypoint.sh" 29 hours ago Created gifted_austin
[ec2-user@ip-10-0-0-70 ~]$

Guess 2:

[ec2-user@ip-10-0-0-70 ~]$ sudo docker run -e DB_HOST=10.0.0.70 -e DB_PORT=3306 -e DB_NAME=<db name> -e DB_USER=<db user> -e DB_PASS=<db pwd> -e DB_TYPE=mysql -e DB_ENV_USER=<superuser> -e DB_ENV_PASS=<superuser pwd> -e SELF_URL_PATH=http://3.65.53.160/ttrss -p 8080:80 ginkel/ttrss

Failed to connect to mysql:host=10.0.0.70;port=3306;dbname=<db name>; (user = <db user>, pw = <db pwd>)
Failed to connect to mysql:host=10.0.0.70;port=3306;dbname=<db name>; (user = <db user>, pw = <db pwd>)
/var/tmp

2021-03-07 17:54:16,597 CRIT Supervisor running as root (no user in config file)
2021-03-07 17:54:16,597 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf.d/ttrss-update-daemon.conf" during parsing
2021-03-07 17:54:16,599 INFO supervisord started with pid 1
2021-03-07 17:54:17,601 INFO spawned: 'nginx' with pid 10
2021-03-07 17:54:17,603 INFO spawned: 'php-fpm' with pid 11
2021-03-07 17:54:17,604 INFO spawned: 'ttrss-update-daemon' with pid 12
[17:54:17/12] Spawn interval: 120 sec

Schema version is wrong, please upgrade the database.

2021-03-07 17:54:17,687 INFO exited: ttrss-update-daemon (exit status 0; not expected)
[07-Mar-2021 17:54:17] NOTICE: fpm is running, pid 11
[07-Mar-2021 17:54:17] NOTICE: ready to handle connections
[07-Mar-2021 17:54:17] NOTICE: systemd monitor interval set to 10000ms
2021-03-07 17:54:18,702 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-03-07 17:54:18,703 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-03-07 17:54:18,704 INFO spawned: 'ttrss-update-daemon' with pid 16
[17:54:18/16] Spawn interval: 120 sec

Schema version is wrong, please upgrade the database.

2021-03-07 17:54:18,740 INFO exited: ttrss-update-daemon (exit status 0; not expected)
2021-03-07 17:54:20,744 INFO spawned: 'ttrss-update-daemon' with pid 17
[17:54:20/17] Spawn interval: 120 sec

Schema version is wrong, please upgrade the database.

2021-03-07 17:54:20,782 INFO exited: ttrss-update-daemon (exit status 0; not expected)
2021-03-07 17:54:23,787 INFO spawned: 'ttrss-update-daemon' with pid 18
[17:54:23/18] Spawn interval: 120 sec

Schema version is wrong, please upgrade the database.

2021-03-07 17:54:23,824 INFO exited: ttrss-update-daemon (exit status 0; not expected)
2021-03-07 17:54:24,825 INFO gave up: ttrss-update-daemon entered FATAL state, too many start retries too quickly

I too had noticed the two messages in apparent antithesis, and usually it would have been enough to reach TTRSS to find the message and upgrade the database, but, to be honest, nothing is displayed: am I building the link wrong?

http://3.65.53.160:8080/ttrss/ <Time to connect has run out Server 3.65.53.160 is taking too long to respond.>

http://3.65.53.160/ttrss/ < Not Found The requested URL was not found on this server.>

I also looked in mysql if there were any new databases, but there aren't any new ones.

Why is the IP address shown in 0.0.0.0?

[ec2-user@ip-10-0-0-70 ~]$ sudo docker container ls --all

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

95874e01f3e2 ginkel/ttrss "/entrypoint.sh" 20 minutes ago Up 20 minutes 0.0.0.0:8080->80/tcp blissful_allen
ab12df10efd3 ginkel/ttrss "/entrypoint.sh" 24 minutes ago Exited (0) 23 minutes ago sleepy_brahmagupta
772fdb76183e ginkel/ttrss "/entrypoint.sh" 27 minutes ago Created suspicious_shirley
1857a48e8e8b ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (0) 24 minutes ago vibrant_shtern
74eedab86452 ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (255) 27 hours ago adoring_bardeen
08a592a519ab ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (0) 27 hours ago practical_saha
95297f64b9b4 ginkel/ttrss "/entrypoint.sh" 27 hours ago Exited (0) 27 hours ago blissful_ptolemy
2bf61371f0a2 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago lucid_brown
82fd0ae7afcc ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago compassionate_ellis
be0e9393d712 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago naughty_wilson
57379ec869aa ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago nervous_margulis
337679505ece ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago suspicious_wescoff
b660374ea152 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago wonderful_kare
f4be7443a86d ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago pensive_margulis
997a0c96f875 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (1) 28 hours ago beautiful_cerf
45320e7ba728 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (1) 28 hours ago wonderful_bhabha
845446b9ca54 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago amazing_shtern
2d0d17a260f7 ginkel/ttrss "/entrypoint.sh" 28 hours ago Exited (255) 28 hours ago xenodochial_jackson
bfb3605376d6 ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 29 hours ago nostalgic_curie
1f2e298e30b4 ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (137) 29 hours ago quirky_mendel
8e31a5576926 ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 29 hours ago festive_bohr
e2a7dccbdc4f ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 29 hours ago gracious_snyder
f4a7a31f0fab ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 29 hours ago goofy_swirles
dab2b501192d ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 29 hours ago trusting_davinci
1ef3f4def609 ginkel/ttrss "/entrypoint.sh" 29 hours ago Exited (255) 29 hours ago jolly_payne
d55f7062bb3d ginkel/ttrss "/entrypoint.sh" 29 hours ago Created gifted_austin
[ec2-user@ip-10-0-0-70 ~]$

Thanks

Massimo

To view this discussion on the web visit https://groups.google.com/d/msgid/simple-groupware/855b5438-4b8e-43b8-9c03-dacdb3a6130bn%40googlegroups.com.

Patrick Pliessnig

unread,

Mar 8, 2021, 8:54:06 AM3/8/21

to Simple Groupware

Hi Massimo

I am afraid I forgot to tell to link urls to the container.

First:

maybe kill and remove all the useless containers and restart with docker run ...

https://stackoverflow.com/questions/45357771/stop-and-remove-all-docker-containers

Second:

- docker creates an sub-network with each container having its own ip-address.

normally the sub-network created is with this mask 172.17.0.0/16 , so the container's ip is somewhere in this range.

you should be able to access the container also with this url http://127.0.0.1:8080/ as you did a port mapping to 8080

- hence, to access the container with an url from the outside, you need to tell your apache to act as a proxy (a gateway) to the container.

- you can do this by telling your apache to create a virtual host and act as proxy for this virtual host

https://stackoverflow.com/questions/46099348/how-to-use-apache-to-redirect-to-docker-container

- when you then call the url http://3.65.53.160/ttrss/

apache should redirect this to http://127.0.0.1:8080/

I hope this helps

Patrick

Reply all

Reply to author

Forward